From: Nicolas Pitre <nico@cam.org>
To: Sam Vilain <sam@vilain.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] [RFC] Generational repacking
Date: Thu, 07 Jun 2007 09:38:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.99.0706070932000.12885@xanadu.home> (raw)
In-Reply-To: <466793EB.2060102@vilain.net>
On Thu, 7 Jun 2007, Sam Vilain wrote:
> Nicolas Pitre wrote:
> >> 2. repack takes too long to run very regularly; it's an occasional
> >> command.
> > It doesn't take long at all when you don't use -a.
>
> Well that depends how many loose objects there are :) I heard about on
> Windows a case where packing 30k loose objects took over an hour.
And your patch cannot change anything to that, right?
You shouldn't wait until 30k loose objects accumulate before repacking.
> >> What I'm aiming for is something which is light enough that it might
> >> even win back the performance loss you got from 1), and to solve the
> >> perception problem of 3).
> >
> > Run git-repack without -a from some hook. You can even launch it in the
> > background.
> >
> > Or what am I missing?
>
> If you repack every 100 objects without -a, sure it will be fast, but
> you'll end up with too many packs.
You just need to adjust this treshold of 100 objects.
And latest GIT behaves _much_ better with lots of packs, almost like if
there was only one pack. See the test results I posted to the list.
Nicolas
next prev parent reply other threads:[~2007-06-07 13:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:08 [PATCH] [RFC] Generational repacking Sam Vilain
2007-06-06 22:46 ` Junio C Hamano
2007-06-06 22:53 ` Sam Vilain
2007-06-07 0:04 ` Dana How
2007-06-07 2:28 ` Sam Vilain
2007-06-07 3:20 ` Nicolas Pitre
2007-06-07 5:13 ` Sam Vilain
2007-06-07 13:38 ` Nicolas Pitre [this message]
2007-06-07 21:29 ` Sam Vilain
2007-06-07 19:46 ` Martin Langhoff
2007-06-07 21:36 ` Sam Vilain
2007-06-07 22:51 ` Martin Langhoff
2007-06-07 3:05 ` 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=alpine.LFD.0.99.0706070932000.12885@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
/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).