From: Jeff King <peff@peff.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] hex: add and use strbuf_add_oid_hex()
Date: Wed, 13 May 2026 12:01:55 -0400 [thread overview]
Message-ID: <20260513160155.GA103037@coredump.intra.peff.net> (raw)
In-Reply-To: <183aa0fd-d455-4ec9-9c42-d511fac8b3e4@web.de>
On Wed, May 13, 2026 at 05:49:11PM +0200, René Scharfe wrote:
> Add a function for adding the full hexadecimal hash value of an object
> ID to a strbuf. It's thread-safe and slightly more efficient than using
> strbuf_addstr() with oid_to_hex() because it doesn't have to determine
> the length of the string or copy it from the intermediate static buffer.
>
> Add and apply a semantic patch to use it throughout the code base.
>
> I get a tiny speedup for git log showing a single hash per commit:
>
> Benchmark 1: ./git_main log --format=%H
> Time (mean ± σ): 91.2 ms ± 0.7 ms [User: 51.9 ms, System: 38.6 ms]
> Range (min … max): 89.8 ms … 92.6 ms 31 runs
>
> Benchmark 2: ./git log --format=%H
> Time (mean ± σ): 90.5 ms ± 0.7 ms [User: 51.0 ms, System: 38.8 ms]
> Range (min … max): 89.2 ms … 92.3 ms 32 runs
Probably the most extreme benchmark would be:
git cat-file --batch-all-objects --batch-check='%(objectname)'
which is really just dumping the oids from packfiles. I got ~3% speedup,
though like yours it's within the run-to-run noise.
I think this is worth doing solely for removing more instances of global
buffers, though.
-Peff
next prev parent reply other threads:[~2026-05-13 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:49 [PATCH] hex: add and use strbuf_add_oid_hex() René Scharfe
2026-05-13 16:01 ` Jeff King [this message]
2026-05-13 16:55 ` René Scharfe
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=20260513160155.GA103037@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.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