On 4/28/2014 12:11 PM, Jon wrote: > Regarding git vs. mercurial on windows, I use both on a daily basis, > like both, but prefer git. The only performance complaint I've had > relates to garbage collection. If you try to `git gc --aggressive > --prune=now` a large repo, you'll often find that the gc fails due to > memory issues even on my 23GB x64 laptop. This is easily solved by > setting the `gc.aggressivewindow` config option to a lower value. I'm > interested in hearing what perf issues John E. has run into.
In general, the larger and older the codebase, the more Git's performance on Windows worsens in comparison to Mercurial's. I've noticed this for day-to-day operations (commits, merges, patch queues / quilts), and even more so for operations requiring deeper historical data -- blames, change histories, etc. This has been my experience with a couple of large codebases (for example, GCC's git mirrors) and I see it corroborated in many other places ([1] for example). Not that I want to start a new VCS holy war. If MinGW-w64 switches to Git, I will grin and bear it. :) -John E. / TDM [1] - <http://blogs.atlassian.com/2012/02/mercurial-vs-git-why-mercurial/> (see also <http://blogs.atlassian.com/2012/03/git-vs-mercurial-why-git/>) ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
