Re: git-fsck/lost-found's speed vs git-prune's

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sep 18, 2007, 11:13 UTC
Message-ID: <Pine.LNX.4.64.0709181211560.28586@racer.site>
In-Reply-To: <20070918095049.GA9388@glandium.org>

Hi,

On Tue, 18 Sep 2007, Mike Hommey wrote:

Show 11 quoted lines

> On Tue, Sep 18, 2007 at 02:18:44AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> > Mike Hommey <mh@glandium.org> writes:
> > 
> > > I was wondering if that was to be expected for git-fsck to be
> > > significantly slower than git-prune (by several orders of magnitude) ?
> > 
> > fsck validates objects are correct and sane.  prune only looks
> > at reachability.
> 
> Now, the speed difference makes sense, but I wouldn't expect lost-found
> to actually bother validating objects...

That's why we should get rid of lost-found, and only keep the --lost-found option to git-fsck, to make it clear.

And I think that it is too rare that you lost objects and want to find them, to warrant a fast version of it.

Ciao, Dscho