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

Re: Reducing the memory footprint

From
Jon Smirl <jonsmirl@gmail.com>
Date
Nov 10, 2007, 01:05 UTC
Message-ID
<9e4733910711091705i6f77d05uc5ba04f668796a73@mail.gmail.com>
In-Reply-To
<20071110005327.GH6212@lavos.net>
On 11/9/07, Brian Downing <bdowning@lavos.net> wrote:
Show 19 quoted lines
> On Fri, Nov 09, 2007 at 06:38:00PM -0500, Jon Smirl wrote:
> > I'm using this config file:
> >
> > [pack]
> >         windowMemory = 1M
> >         deltaCacheSize = 1M
> >
> > And I have NO_MMAP compiled in.
> >
> > git is still using over 200MB of memory or address space, my process
> > gets killed either way.
>
> I'm assuming it's dying on repacking since you included the pack
> parameters.
>
> How big is your biggest object?  Even with pack.windowMemory, it still
> keeps the last object around to try and delta against (in other words,
> the window only shrinks to size 1), which means you have to have room
> for it and its delta index.

It's a Linux kernel repository. Git receive-pack is going over 200MB and getting zapped. I don't understand why the process is so large. I am compiled with -DNO_MMAP.

I think I have a achieved a work around. I rsync'd in my last several weeks of changes. Now I can 'git push' small amounts of changes without getting killed.

I'm begging dreamhost to simply install git. Installed commands don't get zapped.

-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Brian DowningNext: Jon Smirl
Message 3 of 4 in “Reducing the memory footprint”
  1. Jon SmirlNov 9, 2007
  2. Brian DowningNov 10, 2007
  3. Jon SmirlNov 10, 2007
  4. Jon SmirlNov 10, 2007

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.