From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: RAM consumption when working with the gcc repo
Date: Fri, 7 Dec 2007 16:43:58 -0500 [thread overview]
Message-ID: <9e4733910712071343k2d88d2fck1fa3fa333258e8e3@mail.gmail.com> (raw)
In-Reply-To: <20071207213928.GA11613@coredump.intra.peff.net>
On 12/7/07, Jeff King <peff@peff.net> wrote:
> On Fri, Dec 07, 2007 at 03:07:05PM -0500, Jon Smirl wrote:
>
> > I noticed two things when doing a repack of the gcc repo. First is
> > that the git process is getting to be way too big. Turning off the
> > delta caches had minimal impact. Why does the process still grow to
> > 4.8GB?
> >
> > Putting this in perspective, this is a 4.8GB process constructing a
> > 330MB file. Something isn't right. Memory leak or inefficient data
> > structure?
>
> Keep in mind that you are trying many different deltas, which are being
> held in memory, to find the right one and generate the 330MB file. And
> when you multiply that times N threads going at once, _each one_ is
> using a bunch of memory.
>
> As Nico suggested, you could probably drop the memory usage by reducing
> the size of the delta cache.
Delta cache is disabled --
pack.deltacachelimit = 0
Unless this option is broken?
>
> -Peff
>
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2007-12-07 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 20:07 RAM consumption when working with the gcc repo Jon Smirl
2007-12-07 21:24 ` david
2007-12-07 20:36 ` Marco Costalba
2007-12-07 20:46 ` Nicolas Pitre
2007-12-07 21:23 ` Jon Smirl
2007-12-07 21:25 ` Marco Costalba
2007-12-08 11:54 ` Johannes Schindelin
2007-12-08 19:12 ` Marco Costalba
2007-12-07 21:27 ` Jon Smirl
2007-12-07 21:39 ` Jon Smirl
2007-12-07 21:50 ` Jon Smirl
2007-12-08 17:24 ` Martin Koegler
2007-12-07 21:39 ` Jeff King
2007-12-07 21:40 ` Jeff King
2007-12-07 21:43 ` Jon Smirl [this message]
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=9e4733910712071343k2d88d2fck1fa3fa333258e8e3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).