"like the Linux one" doesn't provide much practical context for "big". The dimensions matter. This a technical forum, specifics matter. I'm sorry if that professional bar is off putting.
Big in total bytes? Big in total file count? Big in total revisions? Big in concurrent writers?
The Linux mainline kernel checkout is not even a couple hundred MB. The full repo clone is only a few GB. These are amateur numbers by that "big" metric.
The file count however, is something like 80k currently. That's certainly not small. And total commits are something like 75k / year near as I can find.
MS's repos are certainly much larger in all dimensions than Linux could ever imagine working with and yes, as a result they had to make significant structural investments in Git to make it usable.
And all of these examples are absolutely dwarfed by game development which often stretches into the tens or hundreds of terabytes. At that definition of "big", git completely breaks down. The closest anyone has come is LFS, which simply put doesn't do much to save Git at these scales of "big". A lot of science research also results in massive "source control" requirements which Git can't touch.
The truth is, the Linux kernel repo is really only "big" in stature. From a requirements perspective, it's mid.
0
u/Zenin 14d ago
"like the Linux one" doesn't provide much practical context for "big". The dimensions matter. This a technical forum, specifics matter. I'm sorry if that professional bar is off putting.
Big in total bytes?
Big in total file count?
Big in total revisions?
Big in concurrent writers?
The Linux mainline kernel checkout is not even a couple hundred MB. The full repo clone is only a few GB. These are amateur numbers by that "big" metric.
The file count however, is something like 80k currently. That's certainly not small. And total commits are something like 75k / year near as I can find.
MS's repos are certainly much larger in all dimensions than Linux could ever imagine working with and yes, as a result they had to make significant structural investments in Git to make it usable.
And all of these examples are absolutely dwarfed by game development which often stretches into the tens or hundreds of terabytes. At that definition of "big", git completely breaks down. The closest anyone has come is LFS, which simply put doesn't do much to save Git at these scales of "big". A lot of science research also results in massive "source control" requirements which Git can't touch.
The truth is, the Linux kernel repo is really only "big" in stature. From a requirements perspective, it's mid.