git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git repack memory limit

From
hasen j <hasan.aljudy@gmail.com>
Date
May 19, 2010, 18:45 UTC
Message-ID
<AANLkTil4Mh8wMXpHpqkiUmYyLSIR2AbNaM7KvPNzdQj7@mail.gmail.com>
In-Reply-To
<4BF31045.1000700@l4dev.org>
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.

Previous: Bahadir Balban
Message 2 of 2 in “git repack memory limit”
  1. Bahadir BalbanMay 18, 2010
  2. hasen jMay 19, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.