# git repack memory limit

2 messages from 2010-05-18 to 2010-05-19. Participants: Bahadir Balban, hasen j.
Thread: https://gitlist.dev/t/23839

## Bahadir Balban, 2010-05-18 22:10

Subject: git repack memory limit
Message-ID: <4BF31045.1000700@l4dev.org>
URL: https://gitlist.dev/e/4BF31045.1000700%40l4dev.org

```
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, 2010-05-19 18:45

Subject: Re: git repack memory limit
Message-ID: <AANLkTil4Mh8wMXpHpqkiUmYyLSIR2AbNaM7KvPNzdQj7@mail.gmail.com>
URL: https://gitlist.dev/e/AANLkTil4Mh8wMXpHpqkiUmYyLSIR2AbNaM7KvPNzdQj7%40mail.gmail.com
In-Reply-To: <4BF31045.1000700@l4dev.org>

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

```