From: bdowning@lavos.net (Brian Downing)
To: Nicolas Pitre <nico@cam.org>
Cc: Martin Koegler <mkoegler@auto.tuwien.ac.at>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] pack-objects: only throw away data during memory pressure
Date: Tue, 12 Feb 2008 02:22:12 -0600 [thread overview]
Message-ID: <20080212082211.GE27535@lavos.net> (raw)
In-Reply-To: <alpine.LFD.1.00.0802110942310.2732@xanadu.home>
On Mon, Feb 11, 2008 at 11:00:33AM -0500, Nicolas Pitre wrote:
> On Mon, 11 Feb 2008, Martin Koegler wrote:
> > If pack-objects hit the memory limit, it deletes objects from the
> > delta window.
> >
> > This patch make it only delete the data, which is recomputed, if
> > needed again.
> >
> > Signed-off-by: Martin Koegler <mkoegler@auto.tuwien.ac.at>
>
> Looks fine.
>
> Acked-by: Nicolas Pitre <nico@cam.org>
Unfortunately this patch (if I understand what it's doing correctly)
basically defeats my intended use-case for which I wrote the memory
limiter. I have a repository with files of very mixed size. I want the
window to be very large for small files, for good archival repacking,
but I don't want it to be very large for my 20+MB files with hundreds of
revisions, because I want it to finish someday.
Also, I've gotten into the habit of just doing:
git repack --window=100000 --window-memory=256m
for archival repacks and just letting the memory limit automatically
size the window. Basically, I don't really want to specify a window
size, I just want it to use 512mb of RAM (and go at the speed that size
of a window would entail.) While this is slow, it tends to be a
relatively constant speed, and it tends to find some very interesting
deltas in my trees that I wouldn't have otherwise expected.
If this patch is accepted, I'd really like a way to maintain the old
behavior as an option.
-bcd
next prev parent reply other threads:[~2008-02-12 8:23 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
2008-02-11 16:08 ` Johannes Schindelin
2008-02-11 16:00 ` Nicolas Pitre
2008-02-12 8:22 ` Brian Downing [this message]
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=20080212082211.GE27535@lavos.net \
--to=bdowning@lavos.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
--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).