> From: Konstantin Khomoutov <flatw...@users.sourceforge.net>
> > pack.packsizelimit=2g
> > pack.threads=1
> > pack.windowmemory=256m
> 2. I'd say the pack.packSizeLimit should not affect the packing
> behaviour -- at least that's what I gather from the manual page.
The git-config manual page says:
pack.packSizeLimit
[...] The default is unlimited.
So it seems to me that it is unlikely that pack.packsizeLimit is
affecting memory usage.
On the other hand, the only repository I have that has had memory
problems being repacked is configured:
[pack]
windowMemory = 500m
Is it possible that "pack.packsizelimit=2g" is causing the Git code to
process in a different manner, one in which Git allocates 2G of
memory?
It would be simple to test whether removing that parameter fixes the
symptom.
When I execute the clone (on Fedora Linux), I see no indication of
memory usage that is this large.
Dale
--
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.
