Question

We have some 1,000+ developers in the

Western US (San Francisco Bay Area),

Ottawa Canada,

Bangalore-Hyderabad India,

Stockholm Sweden,

and China.

I would like to have an idea of how long it takes to clone a central repository in the SF Bay Area of 35Gigs/375,000 files in size to other parts of the world, including from SF Bay to SF Bay.

Make all your assumptions about hardware/network ...etc. I just need a ball park number to include on my presentation. (Yes we're looking into Mercurial)

or

if you have your cloning own numbers, would you share them?

thanks in advance

Answer 1

There is some benchmark in Google's document "Analysis of Git and Mercurial":

As a benchmark, Git and Mercurial repositories were seeded with approximately 1500 files totaling 35 M of data. The servers were running in Chicago and the clients in Mountain View (51 ms ping time). The operation of cloning the remote repository (similar to a initial checkout in traditional version control systems) averaged 8.1 seconds for Mercurial and 178 seconds for Git (22 times slower). A single file in the repository was then changed 50 times and the clients pulled the updates. In this case, Mercurial took 1.5 seconds and Git required 18 seconds (12 times slower). When the Git protocol was used instead of HTTP, Git's performance was similar to Mercurial (8.7 seconds for cloning, 2.8 seconds for the pull).

You could look at the original document, but it's all benchmark information from it.