* git repack memory limit
@ 2010-05-18 22:10 Bahadir Balban
2010-05-19 18:45 ` hasen j
0 siblings, 1 reply; 2+ messages in thread
From: Bahadir Balban @ 2010-05-18 22:10 UTC (permalink / raw)
To: git
I am running git-repack on a server with memory limits. I am seeing the
repack spending 400MB and going out of memory. I could not limit repack
memory usage in anyway. I tried:
git config pack.deltaCacheLimit 1
git config pack.deltaCacheSize 1
git config pack.windowMemory 32m
then git repack -a -f -d
also I would particularly expect git repack -a -f -d --window-memory=16
to succeed.
Using git 1.6.5. Any thoughts?
--
Bahadir
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: git repack memory limit
2010-05-18 22:10 git repack memory limit Bahadir Balban
@ 2010-05-19 18:45 ` hasen j
0 siblings, 0 replies; 2+ messages in thread
From: hasen j @ 2010-05-19 18:45 UTC (permalink / raw)
To: Bahadir Balban; +Cc: git
On 18 May 2010 16:10, Bahadir Balban <bahadir@l4dev.org> wrote:
> I am running git-repack on a server with memory limits. I am seeing the
> repack spending 400MB and going out of memory. I could not limit repack
> memory usage in anyway. I tried:
>
> git config pack.deltaCacheLimit 1
> git config pack.deltaCacheSize 1
> git config pack.windowMemory 32m
>
> then git repack -a -f -d
>
> also I would particularly expect git repack -a -f -d --window-memory=16
> to succeed.
>
> Using git 1.6.5. Any thoughts?
>
I ran into a similar situation before.
I believe it loads the entire file to memory, so if you have a single
file that's larger than the available memory, you'll run out of
memory, no matter how you tweak your settings.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-05-19 18:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-18 22:10 git repack memory limit Bahadir Balban
2010-05-19 18:45 ` hasen j
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).