From: Derrick Stolee <stolee@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH] ls-refs: reuse buffer when sending refs
Date: Wed, 25 Aug 2021 10:50:30 -0400 [thread overview]
Message-ID: <705fee2c-7711-ac99-f692-ab08cd7b4e26@gmail.com> (raw)
In-Reply-To: <ccd03e685af0f5cf25c68272a758fc88d115e37a.1629899211.git.ps@pks.im>
On 8/25/2021 9:49 AM, 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.
Reusing a buffer makes perfect sense and is a clear improvement.
> 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>
> ---
>
> Note that while this topic applies on top of "master", I've done the
> benchmark on top of my other optimizations for fetches. It's cheating a
> bit, but it's easier to see that the optimization does something when
> the remaining constant part is lower.
I don't mind demonstrating an optimization using the other work.
Perhaps this would be better grouped with those other changes?
I know that the text is independent and merges cleanly without it,
but it can be helpful to think about the effort as one unified
topic instead of juggling multiple, especially because I don't
see the other one needing many revisions.
> - struct strbuf refline = STRBUF_INIT;
> +
> + strbuf_reset(&data->buf);
It's nice that this is the only _real_ change, and everything
else is a find-and-replace.
> @@ -145,6 +146,7 @@ int ls_refs(struct repository *r, struct strvec *keys,
>
> memset(&data, 0, sizeof(data));
> strvec_init(&data.prefixes);
> + strbuf_init(&data.buf, 0);
>
> ensure_config_read();
> git_config(ls_refs_config, NULL);
> @@ -173,6 +175,7 @@ int ls_refs(struct repository *r, struct strvec *keys,
> send_ref, &data, 0);
> packet_flush(1);
> strvec_clear(&data.prefixes);
> + strbuf_release(&data.buf);
> return 0;
> }
Except, of course, these two lines.
I think this patch is good to go!
Thanks,
-Stolee
next prev parent reply other threads:[~2021-08-25 14:50 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
2021-08-25 14:50 ` Derrick Stolee [this message]
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=705fee2c-7711-ac99-f692-ab08cd7b4e26@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).