From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Taylor Blau" <me@ttaylorr.com>, "Rohit Ner" <rohitner1@gmail.com>
Cc: "Derrick Stolee" <derrickstolee@github.com>, git@vger.kernel.org
Subject: Re: git log causing hang while browsing upstream linux
Date: Tue, 11 Apr 2023 11:45:47 +0200 [thread overview]
Message-ID: <a356d9d4-e7e5-460d-bf90-b9d51649a20b@app.fastmail.com> (raw)
In-Reply-To: <ZDSjBQhyDBGi9wBN@nand.local>
On Tue, Apr 11, 2023, at 02:00, Taylor Blau wrote:
> TL;DR: if you run "git commit-graph write" once before running "git log
> --oneline --graph", you'll get near-instantaneous results.
Cool! Testing on Linux repo:
Without it:
$ time git log --oneline --graph | head -1
* 0d3eb744aed4 Merge tag 'urgent-rcu.2023.04.07a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
real 0m11.379s
user 0m10.655s
sys 0m0.726s
With it:
$ time git log --oneline --graph | head -1
* 0d3eb744aed4 Merge tag 'urgent-rcu.2023.04.07a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
real 0m0.032s
user 0m0.014s
sys 0m0.023s
Maybe I’m gonna enable `git maintenance` for my repos. :)
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2023-04-11 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 20:13 git log causing hang while browsing upstream linux Rohit Ner
2023-04-04 20:27 ` Kristoffer Haugsbakk
2023-04-04 20:50 ` Kristoffer Haugsbakk
2023-04-10 17:07 ` Rohit Ner
2023-04-11 0:00 ` Taylor Blau
2023-04-11 9:45 ` Kristoffer Haugsbakk [this message]
2023-04-16 7:09 ` SZEDER Gábor
2023-04-16 12:46 ` How to write to the commit graph on clone? Kristoffer Haugsbakk
2023-04-16 15:24 ` Ævar Arnfjörð Bjarmason
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=a356d9d4-e7e5-460d-bf90-b9d51649a20b@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=rohitner1@gmail.com \
/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).