git repack memory limit

Bahadir Balban· May 18, 2010, 22:10 UTC · lore

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

hasen j· May 19, 2010, 18:45 UTC · re: Bahadir Balban · lore

Re: git repack memory limit

On 18 May 2010 16:10, Bahadir Balban <bahadir@l4dev.org> wrote:

Show 15 quoted lines

> 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.