From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Subject: Re: [PATCH] ls-refs: reuse buffer when sending refs
Date: Wed, 25 Aug 2021 16:10:25 +0200 [thread overview]
Message-ID: <YSZPUYk5J10DID+7@ncase> (raw)
In-Reply-To: <ccd03e685af0f5cf25c68272a758fc88d115e37a.1629899211.git.ps@pks.im>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Wed, Aug 25, 2021 at 03:49:51PM +0200, Patrick Steinhardt wrote:
> In the initial reference advertisement, the Git server will first
> announce all of its references to the client. The logic is handled in
> `send_ref()`, which will allocate a new buffer for each refline it is
> about to send. This is quite wasteful: instead of allocating a new
> buffer each time, we can just reuse a buffer.
>
> Improve this by passing in a buffer via the `ls_refs_data` struct which
> is then reused on each reference. In a repository with about 2.3M refs,
> this speeds up local mirror fetches by about 2%:
>
> Benchmark #1: HEAD~: git-fetch
> Time (mean ± σ): 25.415 s ± 0.131 s [User: 22.722 s, System: 4.740 s]
> Range (min … max): 25.240 s … 25.543 s 5 runs
>
> Benchmark #2: HEAD: git-fetch
> Time (mean ± σ): 24.922 s ± 0.110 s [User: 22.404 s, System: 4.476 s]
> Range (min … max): 24.825 s … 25.081 s 5 runs
>
> Summary
> 'HEAD: git-fetch' ran
> 1.02 ± 0.01 times faster than 'HEAD~: git-fetch'
>
> Signed-off-by: Patrick Steinhardt <ps@kps.im>
I accidentally mis-typed my mail here. Really shows I should be using
`--signoff` instead of manually signing things. Anyway, I'll fix this in
case I'll need to re-roll.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-08-25 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 13:49 [PATCH] ls-refs: reuse buffer when sending refs Patrick Steinhardt
2021-08-25 14:10 ` Patrick Steinhardt [this message]
2021-08-25 14:50 ` Derrick Stolee
2021-08-25 15:43 ` Patrick Steinhardt
2021-08-25 17:23 ` 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=YSZPUYk5J10DID+7@ncase \
--to=ps@pks.im \
--cc=git@vger.kernel.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 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.