author | Nicolas Pitre <nico@cam.org> | |
Wed, 5 Aug 2009 20:55:07 +0000 (16:55 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 6 Aug 2009 03:14:54 +0000 (20:14 -0700) | ||
commit | 5749b0b2f935dc418c98ba8e7c52c3291451bc4a | |
tree | 67e34e7cbc3b1bf0fa6bdf8f64c6859fc729416f | tree | snapshot |
parent | f0df1293acdba9513cae17e2c63b4169f1347371 | commit | diff |
don't let the delta cache grow unbounded in 'git repack'
I have 4GB of RAM on my system which should, in theory, be quite enough
to repack a 600 MB repository. However the unbounded delta cache size
always pushes it into swap, at which point everything virtually comes to
a halt. So unbounded caches are never a good idea.
A default of 256MB should be a good compromize between memory usage and
speed where medium sized repositories are still likely to fit in the
cache with a reasonable memory usage, and larger repositories are going
to take quite some time to repack already anyway.
While at it, clarify the associated config variable documentation
entries a bit.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
I have 4GB of RAM on my system which should, in theory, be quite enough
to repack a 600 MB repository. However the unbounded delta cache size
always pushes it into swap, at which point everything virtually comes to
a halt. So unbounded caches are never a good idea.
A default of 256MB should be a good compromize between memory usage and
speed where medium sized repositories are still likely to fit in the
cache with a reasonable memory usage, and larger repositories are going
to take quite some time to repack already anyway.
While at it, clarify the associated config variable documentation
entries a bit.
Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/config.txt | diff | blob | history | |
builtin-pack-objects.c | diff | blob | history |