From: david@lang.hm
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: RAM consumption when working with the gcc repo
Date: Fri, 7 Dec 2007 13:24:41 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0712071323260.12607@asgard.lang.hm> (raw)
In-Reply-To: <9e4733910712071207p750c14f4h7abc5d637da3a478@mail.gmail.com>
On Fri, 7 Dec 2007, 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 that 330MB file is _very_ heavily compressed. the simple
zlib compression is probably getting you 10:1 or 20:1 compression and the
delta compression is a significant multiplier on top of that.
David Lang
> The second issue is that the repack process slows way down on the last
> 10% of the packing process. I don't believe this was caused by
> swapping since my disk light wasn't on. It takes a long to do the last
> 10% as it did for the first 70%. This seems to be correlated with the
> size of the process getting so large.
>
>
next prev parent reply other threads:[~2007-12-07 20:16 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 [this message]
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
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=Pine.LNX.4.64.0712071323260.12607@asgard.lang.hm \
--to=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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).