From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: git gc expanding packed data?
Date: Wed, 12 Aug 2009 15:45:16 +0100 [thread overview]
Message-ID: <3ace41890908120745y305b2a59hd453b7e146e4a774@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0908111718490.10633@xanadu.home>
On Tue, Aug 11, 2009 at 10:33 PM, Nicolas Pitre<nico@cam.org> wrote:
<snipped>
> From git v1.6.3 the --aggressive switch makes for 'git repack' to be
> called with --window=250 --depth=250, meaning the equivalent of:
>
> git repack -a -d -f --window=250 --depth=250
>
> Do you still get a huge pack with the above?
>
>> I guess --aggressive doesn't always save space...
>
> If so that is (and was) a bug.
I tried 'git repack -a -d -f --window=250 --depth=250' with 1.6.2.5
(fc11.x86_64) and it took half a day, swallowed up all the memory -
3GB virtual & 1.3GB resident - and finally the kernel oom killer
killed it at a last message of (601460/957910). Left no temp files.
Would git 1.6.3 use less memory? :-(
Hin-Tak
next prev parent reply other threads:[~2009-08-12 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 20:25 git gc expanding packed data? Hin-Tak Leung
2009-08-05 22:39 ` Nicolas Pitre
2009-08-11 10:17 ` Hin-Tak Leung
2009-08-11 21:33 ` Nicolas Pitre
2009-08-12 14:45 ` Hin-Tak Leung [this message]
2009-08-12 15:35 ` Nicolas Pitre
2009-08-13 17:31 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2009-08-08 1:11 Andreas Schwab
2009-08-08 13:05 ` Hin-Tak Leung
2009-08-08 13:25 ` Andreas Schwab
2009-08-09 2:56 ` Nicolas Pitre
2009-08-09 7:43 ` Andreas Schwab
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=3ace41890908120745y305b2a59hd453b7e146e4a774@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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).