Git development
 help / color / mirror / Atom feed
From: "Dana How" <danahow@gmail.com>
To: "Brian Downing" <bdowning@lavos.net>
Cc: git@vger.kernel.org, danahow@gmail.com
Subject: Re: [RFC] Dynamic window size on repack?
Date: Sun, 8 Jul 2007 14:35:05 -0700	[thread overview]
Message-ID: <56b7f5510707081435h60c1787br16cf389161d7143@mail.gmail.com> (raw)
In-Reply-To: <20070708211606.GF4087@lavos.net>

On 7/8/07, Brian Downing <bdowning@lavos.net> wrote:
> I have a CVS repository which is mostly sane, but has an approximately
> 20MB RTF file that has two hundred revisions or so.  (Thank you, Windows
> help.)
>
> Now, since this is old history, I want to make it as small as possible.
> The only problem is that when I use high --window values for repack,
> it goes along swimmingly until it gets to this file, at which point
> memory usage quickly rises to the point where I'm well into my swap file.
>
> I think what I'd like is an extra option to repack to limit window
> memory usage.  This would dynamically scale the window size down if it
> can't fit within the limit, then scale it back up once you're off of the
> nasty file.  This would let me repack my repository with --window=100
> and have it actually finish someday on the machines I have access to.
> The big file may not be as efficiently packed as possible, but I can
> live with that.
>
> My question is, is this sane?  Does the repack algorithm depend on having
> a fixed window size to work?  I'd rather not look into implementing this
> if it's silly on the face of it.

Sounds very sane to me.

It seems like you want something like this
(I've not referred to the code,  but there is a loop
 that could be modifed to include something like this):
  /* build list of delta candidates */
  tot = 0;
  for (i = 0; i < window; ++i ) {
    obj = objects_sorted_for_delta[here + i];
    tot += SIZE(obj);
    if ( tot > window_limit )
      break;
    /* insert obj in list of things to delta, or just try it here */
    ...
  }
  if ( i <= 1 )
    break/return;

window_limit could be set automatically like the variables
for the mmap windows are (no new options).
SIZE() should be defined to return the actual bytes consumed
by the object (I think for this it's uncompressed and undeltified,
but as I said I haven't looked at the code).

It would be better if the current list of objects in the window
were a FIFO.  Before each deltification attempt,  add objects
from the sort list until #objects > window or tot > window_limit.
After each attempt, drop off the object we were trying to delta.

I like your idea and think you should look into implementing it.
-- 
Dana L. How  danahow@gmail.com  +1 650 804 5991 cell

  reply	other threads:[~2007-07-08 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 21:16 [RFC] Dynamic window size on repack? Brian Downing
2007-07-08 21:35 ` Dana How [this message]
2007-07-08 21:35 ` Linus Torvalds
2007-07-08 21:39   ` Linus Torvalds

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=56b7f5510707081435h60c1787br16cf389161d7143@mail.gmail.com \
    --to=danahow@gmail.com \
    --cc=bdowning@lavos.net \
    --cc=git@vger.kernel.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