4 ms·
I call bullshit on "our repository is too big for one machine". Seriously, you have over 1 TB of code and 100 people wrote it?
by ajuc 8y ago
I call bullshit on "our repository is too big for one machine".
Seriously, you have over 1 TB of code and 100 people wrote it?
- dmarlow 8y agoYou can have large repos and it not only be code. I remember seeing repos many tens of gigs because all of VS was versioned as well for "reproducibility".
- Xylakant 8y agoadding raw versions of binary assets (designs, video, ...) can quickly lift a repo beyond a TB. Now, you could say "don't do that", but there's valid use cases where you'd want to track all binary assets as part of the development cycle.
- tome 8y agoOuch, well, yes that is a very good situation in which not to take the "mono" part of "monorepo" too seriously.
- daemin 8y agoYou can do that with content, you just partition the workspace/view of the monorepo to what each person needs rather than checking the entire thing out git style.
- Xylakant 8y agoor use a VCS that allows partial checkouts of repositories. There's no DVCS that I know of that can do that, but for example SVN can. Git LFS might be an option, too. There are also commercial products that target that market. I just wanted to point out that reaching a measly TB of data doesn't require much effort. (worked on a product that would version rendered clips for special effect production).
- dllthomas 8y agoSee also: https://git-annex.branchable.com https://git-annex.branchable.com
- bpicolo 8y agoIn 2016, Google's monorepo was 86TB
- manigandham 8y agoThe keyword there is "Google". Everything is different at the extremes.