You mean like Teslas multi terabyte repo is not normal?
replyI think it's obvious that multi terabyte repos are not the norm.
replyHow did they even manage to generate a terabyte sized repo, that's crazy. Do they have something written up on how it's structured and why they'd even go that route?
replyIt couldn’t be broken in to domain specific components?
replyListen, I am a rails developer, so a monolith doesn’t scare me, and yet, there are limits. Why does it need to be a multi terabyte monolith?
Ever work on a AAA game?
replyThat probably mostly assets, no?
replyProbably, but you want to version control assets too.
replyPeople usually mention git-lfs at this point, but that is always annoying to use in practice. There is also shallow-clones and sparse-checkouts, but these only mitigate the problem as there is no way around cloning at least one revision completely with git.
My last project was about 400Gb, and probably 2M lines of C++. The days size is mostly assets but there’s still a lot of code.
reply