From: Nicolas Pitre <nico@cam.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Martin Koegler <mkoegler@auto.tuwien.ac.at>, git@vger.kernel.org
Subject: Re: [PATCH] pack-objects: only throw away data during memory pressure
Date: Mon, 11 Feb 2008 11:00:25 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802111054080.2732@xanadu.home> (raw)
In-Reply-To: <alpine.LSU.1.00.0802111519300.3870@racer.site>
On Mon, 11 Feb 2008, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 11 Feb 2008, Martin Koegler wrote:
>
> > What about this not really tested patch for dealing with memory pressure
> > in git-pack-objects?
> >
> > It will slow down the repack in the case of memory pressure, but missing
> > memory will not affect the results.
>
> It almost helped:
>
> $ /usr/bin/time git repack -a -d -f --window=250 --depth=250
> Counting objects: 2477715, done.
> fatal: Out of memory, malloc failed411764)
> Command exited with non-zero status 1
> 10050.12user 240.63system 2:53:37elapsed 98%CPU (0avgtext+0avgdata
> 0maxresident)k
> 0inputs+0outputs (29555major+94032945minor)pagefaults 0swaps
>
> So, it ran longer until it ran out of memory.
What it can do for you is to limit the window memory usage much more
without affecting the end result, say to 128MB. Of course the repack is
then going to progress much slower if active purging of the window
memory is involved.
If you still run out of memory at that point then there is not much more
to do besides using a new memory allocator that doesn't suffer as much
from memory fragmentation, or find the possible memory leak that no one
else found so far.
Nicolas
next prev parent reply other threads:[~2008-02-11 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 7:26 [PATCH] pack-objects: only throw away data during memory pressure Martin Koegler
2008-02-11 15:20 ` Johannes Schindelin
2008-02-11 16:00 ` Nicolas Pitre [this message]
2008-02-11 16:08 ` Johannes Schindelin
2008-02-11 16:00 ` Nicolas Pitre
2008-02-12 8:22 ` Brian Downing
2008-02-12 14:26 ` Nicolas Pitre
2008-02-12 17:14 ` Brian Downing
2008-02-12 17:17 ` Brian Downing
2008-02-12 17:28 ` Brian Downing
2008-02-12 17:39 ` Nicolas Pitre
2008-02-13 1:48 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.00.0802111054080.2732@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).