Linked by Thom Holwerda on Wed 24th May 2017 20:02 UTC

Over the past 3 months, we have largely completed the rollout of Git/GVFS to the Windows team at Microsoft.

As a refresher, the Windows code base is approximately 3.5M files and, when checked in to a Git repo, results in a repo of about 300GB. Further, the Windows team is about 4,000 engineers and the engineering system produces 1,760 daily "lab builds" across 440 branches in addition to thousands of pull request validation builds. All 3 of the dimensions (file count, repo size and activity), independently, provide daunting scaling challenges and taken together they make it unbelievably challenging to create a great experience. Before the move to Git, in Source Depot, it was spread across 40+ depots and we had a tool to manage operations that spanned them.

As of my writing 3 months ago, we had all the code in one Git repo, a few hundred engineers using it and a small fraction (<10%) of the daily build load. Since then, we have rolled out in waves across the engineering team.

Permalink for comment 644877
To read all comments associated with this story, please click here.
RE[3]: Too many cooks...
by avgalen on Mon 29th May 2017 09:50 UTC in reply to "RE[2]: Too many cooks..."
Member since:

As you can see you can blame a lot on Vista, but there is no "1000x times increase" over the last 30 years and in the last 10 years there has basically been no increase in hardware requirements at all even though hardware DID actually get faster. Conclusion: no absolute bloat, less relative bloat, happier users!

Also, comparing NT 3.1 to "10" is pretty much like comparing an arrow to a machine gun. All that extra code and used resource didn't just go to waste and a "10" machine now is a whole lot cheaper than a NT "3.1" machine used to be

Reply Parent Score: 2