I'm experiencing very slow git pushes. On the order of 1 minute to push a 
trivial one-line change. When I set GIT_TRACE=1, I see that it seems to be 
taking a lot of time in the pack-objects phase. 

Others are not seeing this with the same repo, but I'm the only one working 
in a VM.

~/ws/git/repo.1/repo > date; git push smorton; date
Wed Mar  4 15:03:11 EST 2015
15:03:11.086758 git.c:349               trace: built-in: git 'push' 
'smorton'
15:03:11.126665 run-command.c:341       trace: run_command: 'ssh' '-p' 
'7999' 'git@privacy.privacy' 'git-receive-pack '\''~smorton/repo.git'\'''
15:03:20.383341 run-command.c:341       trace: run_command: 'pack-objects' '
--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '
--progress'
15:03:20.383945 exec_cmd.c:134          trace: exec: 'git' 'pack-objects' '
--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '
--progress'
15:03:20.385168 git.c:349               trace: built-in: git 'pack-objects' 
'--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' 
'--progress'
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 20.86 KiB | 0 bytes/s, done.
Total 4 (delta 0), reused 0 (delta 0)
To ssh://git@privacy.privacy:7999/~smorton/repo.git
   5fe662f..a137bda  my_branch -> my_branch
Wed Mar  4 15:04:22 EST 2015

After it was slow at first, I tried setting these which did not help

repack.writebitmaps=true
pack.windowmemory=100m



Details:
git version 2.1.4
OS: CentOS 6.6 64-bit *in a VM*. 
repo size: huge. 6 GB .git directory, around 800 MB working tree.
VM has 8 MB RAM and 8 cores.
CPU: i7, 8 core (4 cores hyperthreaded)



Any ideas?
Thanks.

Steve

-- 
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/d/optout.

Reply via email to