From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
gcc@gcc.gnu.org, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Something is broken in repack
Date: Tue, 11 Dec 2007 16:34:00 -0000 [thread overview]
Message-ID: <9e4733910712110821o7748802ag75d9df4be8b2c123@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.99999.0712111117440.555@xanadu.home>
On 12/11/07, Nicolas Pitre <nico@cam.org> wrote:
> On Tue, 11 Dec 2007, Nicolas Pitre wrote:
>
> > OK, here's something else for you to try:
> >
> > core.deltabasecachelimit=0
> > pack.threads=2
> > pack.deltacachesize=1
> >
> > With that I'm able to repack the small gcc pack on my machine with 1GB
> > of ram using:
> >
> > git repack -a -f -d --window=250 --depth=250
> >
> > and top reports a ~700m virt and ~500m res without hitting swap at all.
> > It is only at 25% so far, but I was unable to get that far before.
>
> Well, around 55% memory usage skyrocketed to 1.6GB and the system went
> deep into swap. So I restarted it with no threads.
>
> Nicolas (even more puzzled)
On the plus side you are seeing what I see, so it proves I am not imagining it.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-12-11 16:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e4733910712071505y6834f040k37261d65a2d445c4@mail.gmail.com>
[not found] ` <9e4733910712101825l33cdc2c0mca2ddbfd5afdb298@mail.gmail.com>
[not found] ` <alpine.LFD.0.99999.0712102231570.555@xanadu.home>
[not found] ` <9e4733910712102125w56c70c0cxb8b00a060b62077@mail.gmail.com>
2007-12-11 7:01 ` Jon Smirl
2007-12-11 7:34 ` Jon Smirl
2007-12-11 11:11 ` Andreas Ericsson
2007-12-11 15:01 ` Nicolas Pitre
2007-12-11 15:36 ` Nicolas Pitre
2007-12-11 16:20 ` Jon Smirl
2007-12-11 16:22 ` Nicolas Pitre
2007-12-11 16:34 ` Jon Smirl [this message]
2007-12-12 7:25 ` Nicolas Pitre
2007-12-12 12:02 ` David Kastrup
2007-12-14 16:44 ` Wolfram Gloger
2007-12-12 16:14 ` Nicolas Pitre
2007-12-12 16:37 ` Paolo Bonzini
2007-12-12 16:42 ` Linus Torvalds
2007-12-12 16:54 ` David Miller
2007-12-12 17:12 ` Linus Torvalds
2007-12-12 17:29 ` Jon Smirl
2007-12-14 16:19 ` Wolfram Gloger
2007-12-14 16:59 ` David Kastrup
2007-12-14 18:49 ` Wolfram Gloger
2007-12-13 14:09 ` Nguyen Thai Ngoc Duy
[not found] ` <fjrj9k$n6k$1@ger.gmane.org>
2007-12-13 16:39 ` Paolo Bonzini
2007-12-13 17:40 ` Johannes Sixt
2007-12-14 2:31 ` Jakub Narebski
[not found] ` <fjt6vm$n7d$1@ger.gmane.org>
2007-12-14 6:39 ` Nguyen Thai Ngoc Duy
2007-12-14 9:02 ` Paolo Bonzini
2007-12-14 9:39 ` Harvey Harrison
2007-12-14 10:52 ` Jakub Narebski
2007-12-14 13:25 ` Nguyen Thai Ngoc Duy
2007-12-14 13:53 ` Nicolas Pitre
2007-12-12 16:19 ` Nicolas Pitre
2007-12-13 7:39 ` Andreas Ericsson
2007-12-14 16:12 ` Wolfram Gloger
2007-12-11 17:19 ` Linus Torvalds
2007-12-11 17:24 ` Nicolas Pitre
2007-12-11 17:28 ` David Miller
2007-12-11 18:43 ` Nicolas Pitre
2007-12-11 20:34 ` Andreas Ericsson
2007-12-11 18:57 ` Jon Smirl
2007-12-11 19:17 ` Nicolas Pitre
2007-12-11 19:40 ` Linus Torvalds
2007-12-11 20:26 ` Junio C Hamano
2007-12-12 5:06 ` Andreas Ericsson
2007-12-11 17:44 ` Daniel Berlin
2007-12-11 13:49 ` 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=9e4733910712110821o7748802ag75d9df4be8b2c123@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).