From: Sam Vilain <sam@vilain.net>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: git-fsck/lost-found's speed vs git-prune's
Date: Tue, 18 Sep 2007 21:14:37 +1200 [thread overview]
Message-ID: <46EF96FD.1050602@vilain.net> (raw)
In-Reply-To: <20070918090926.GA8927@glandium.org>
Mike Hommey wrote:
> Hi,
>
> I was wondering if that was to be expected for git-fsck to be
> significantly slower than git-prune (by several orders of magnitude) ?
>
> $ time git-lost-found
>
> real 8m22.167s
> user 6m44.153s
> sys 1m16.613s
>
> $ time git-prune
>
> real 0m0.376s
> user 0m0.304s
> sys 0m0.000s
>
You're probably already packed. I'd expect a similar speed difference
between git-fsck and git-fsck --full.
Sam.
next prev parent reply other threads:[~2007-09-18 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 9:09 git-fsck/lost-found's speed vs git-prune's Mike Hommey
2007-09-18 9:14 ` Sam Vilain [this message]
2007-09-18 9:18 ` Junio C Hamano
2007-09-18 9:50 ` Mike Hommey
2007-09-18 11:13 ` Johannes Schindelin
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=46EF96FD.1050602@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).