From: Patrick Steinhardt <ps@pks.im>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Karthik Nayak <karthik.188@gmail.com>
Subject: Re: Poor performance using reftable with many refs
Date: Thu, 13 Feb 2025 07:11:33 +0100 [thread overview]
Message-ID: <Z62NFXja4CkrxSil@pks.im> (raw)
In-Reply-To: <Z602dzQggtDdcgCX@tapette.crustytoothpaste.net>
On Thu, Feb 13, 2025 at 12:01:59AM +0000, brian m. carlson wrote:
> It takes about 30 times as long to perform using the reftable backend,
> which is concerning. While this is a synthetic measurement, I had
> intended to use it to determine the performance characteristics of
> the reference update portion when pushing a large repository for the
> first time.
Interesting, that's an edge case I didn't yet see. I know about some
cases where reftables are ~10% slower, but 30x slower is in a different
ballpark.
> I admit I haven't done any other particular investigation as to what's
> going wrong here, but the behaviour is very noticeable so it may be easy
> to profile.
No worries, I'm already happy to have gotten the report in the first
place :) I'll investigate, but probably won't get to it before next
week.
Thanks!
Patrick
next prev parent reply other threads:[~2025-02-13 6:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 0:01 Poor performance using reftable with many refs brian m. carlson
2025-02-13 6:11 ` Patrick Steinhardt [this message]
2025-02-13 7:13 ` Patrick Steinhardt
2025-02-13 8:22 ` Jeff King
2025-02-13 11:20 ` Patrick Steinhardt
2025-02-13 14:31 ` Patrick Steinhardt
2025-02-13 19:53 ` Jeff King
2025-02-13 19:42 ` Jeff King
2025-02-13 20:12 ` Junio C Hamano
2025-02-13 22:17 ` brian m. carlson
2025-02-13 9:27 ` Christian Couder
2025-02-13 13:21 ` Patrick Steinhardt
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=Z62NFXja4CkrxSil@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.