On Monday, July 22, 2013 8:28:03 AM UTC+2, Teddy wrote:

> Dear all,
> Has anyone got ideas to boost the git performance on windows?
> I am testing git on windows 2012 64 bit server (testing environment) with 
> latest git 1.8.3.
> Intel Xeon @2.5 GHz 12 cores (24 threads) with 32 GB RAM.
> Here are the tweaks i've done so far :
> - uninstall non critical software
> - disable firewall 

This is generally a bad idea. I doubt a firewall will have an effect on 
performance by itself. Either it will block traffic entirely, or if 
correctly configured, allow traffic to pass through. If some firewall does 
packet inspection on the fly, this should only affect git pull/push/fetch, 
which you don't do so often anyway.

> - not using any antivirus
Again, this is a bad idea. Perhaps you can set your antivirus software to 
exclude any on-the-fly scanning of your git repositories (c:\projects\ or 
whatever), or schedule scans to run at intervals where you are not using 

> - disable non critical windows services
> - set windows performance options ==> "adjust for best performance"

Maybe those two are generally good advice for Windows users, but I doubt 
they will add much to Git performance directly. 

> - use git portable

I don't see why using git 
 offer an advantage (?).

> - disabled the UAC

As with the firewall above: Either Windows will block your operations, or 
it will allow it without limiting performance (unless Windows checks 
permissions on every micro-operation - I'm not a Windows expert so someone 
else will have to correct me on this if I'm in the wrong here).

Compared to the git performance on linux, the git on windows are wayyyy 
> slower.
> Example on linux : 1 min, on windows : 13 mins

It would be more useful if you would include what Git commands you are 
using here, and what the size of the repository is.

> Anyone can suggest other improvements?

How about working on SSD-drives? Since Git is largely file-system based 
(and I'm guessing a large part of Linux' performance advantage comes from 
cleverly caching file-system reads in memory), running on SSD could offer 
some big improvements.

If you are doing some kind of one-off operations or analysis, and you just 
need a really fast Git repository for the day, you could try cloning onto a RAM 
disk <http://en.wikipedia.org/wiki/List_of_RAM_drive_software> and do the 
operations there. Just remember to clone back onto a proper disk regularly 
or before you reboot, so you don't lose data. 

I'll also CC the msysgit list as this is up their alley. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to