From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: "git reflog expire --all" very slow
Date: Mon, 30 Mar 2009 22:50:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0903302244580.4093@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0903302231370.4093@localhost.localdomain>
On Mon, 30 Mar 2009, Linus Torvalds wrote:
>
> If I do
>
> mark_reachable(cb.ref_commit, 0);
Ok, I think I got it.
You had
mark_reachable(cb.ref_commit, cmd->expire_unreachable);
but we care about the commits that are younger than 'expire_total' (older
than that, and they are pruned unconditionally), but older than
'expire_unreachable' (younger than that and the date doesn't matter).
So making it do
mark_reachable(cb.ref_commit, cmd->expire_total);
marks the right parts reachable. Not the whole tree, but also not just the
commits we're not going to expire regardless.
With that change, it's all basically instantaneous. We don't need to
traverse the whole kernel history, and with that change to your patch, I
get
[torvalds@nehalem linux]$ time ~/git/git reflog expire --all
real 0m1.715s
user 0m1.676s
sys 0m0.040s
which is still slower than I'd wish for, but is a whole lot faster than
over half a minute.
Linus
next prev parent reply other threads:[~2009-03-31 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 1:43 "git reflog expire --all" very slow Linus Torvalds
2009-03-31 4:34 ` Junio C Hamano
2009-03-31 5:09 ` Linus Torvalds
2009-03-31 5:24 ` Junio C Hamano
2009-03-31 5:42 ` Linus Torvalds
2009-03-31 5:57 ` Junio C Hamano
2009-03-31 5:50 ` Junio C Hamano
2009-03-31 5:38 ` Linus Torvalds
2009-03-31 5:50 ` Linus Torvalds [this message]
2009-03-31 5:51 ` Linus Torvalds
2009-04-02 6:46 ` Junio C Hamano
2009-04-02 15:30 ` Linus Torvalds
2009-03-31 6:08 ` Junio C Hamano
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.2.00.0903302244580.4093@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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).