From: Nicolas Pitre <nico@cam.org>
To: Sam Vilain <sam@vilain.net>
Cc: Dana How <danahow@gmail.com>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] [RFC] Generational repacking
Date: Wed, 06 Jun 2007 23:20:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.99.0706062314410.12885@xanadu.home> (raw)
In-Reply-To: <46676D44.7070703@vilain.net>
On Thu, 7 Jun 2007, Sam Vilain wrote:
> Dana How wrote:
> > This patch complicates git-repack.sh quite a bit and
> > I'm unclear on what _problem_ you're addressing.
>
> The problem is simple, and it is partially in the eye of the beholder.
>
> That is;
>
> 1. without repacking, you get a lot of loose objects.
> - unnecessary disk space usage
> - bad performance on many OSes
No argument.
> 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.
> 3. the perception that git repositories are not maintenance free.
But this perception is true! It is possible to automate it, but some
maintenance is necessary at some point.
> 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?
Nicolas
next prev parent reply other threads:[~2007-06-07 3:22 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 [this message]
2007-06-07 5:13 ` Sam Vilain
2007-06-07 13:38 ` Nicolas Pitre
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.0706062314410.12885@xanadu.home \
--to=nico@cam.org \
--cc=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).