From: Patrick Steinhardt <ps@pks.im>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org, Ted Nyman <tnyman@openai.com>
Subject: Re: [PATCH 0/2] fetch-pack: allow parallelizing packfile URI fetches
Date: Mon, 31 Aug 2026 07:43:38 +0200 [thread overview]
Message-ID: <apUUiv4SD0-W8QS3@pks.im> (raw)
In-Reply-To: <apSpaLf_Pu3G4Nqm@denethor>
On Sun, Aug 30, 2026 at 09:33:52PM -0500, Justin Tobler wrote:
> On 26/08/21 02:31PM, Patrick Steinhardt wrote:
> > Hi,
> >
> > this patch series prepares git-fetch(1) and git-clone(1) to handle
> > fetches of packfile URIs in parallel. This can significantly speed up
> > fetches when the server announces a bunch of packfiles, as shown in the
> > benchmarks in the second patch.
>
> So I've been working on a series to extend the use of the ODB
> transaction interface to also cover fetch-pack. As part of this, my
> current plan was to also refactor fetching packfile URIs so that they
> can be written through `odb_transaction_write_pack()`. I like what this
> series is doing, but I wonder if it might a bit more straightforward if
> we try to land transaction here first. Otherwise, I think we may end up
> having to redo some of these changes to get parallelizing packfile URI
> fetches to work.
I'm fine to drop this series for now in favor of yours. I'll resend once
your series has been merged. Thanks!
Patrick
prev parent reply other threads:[~2026-08-31 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 12:31 [PATCH 0/2] fetch-pack: allow parallelizing packfile URI fetches Patrick Steinhardt
2026-08-21 12:31 ` [PATCH 1/2] fetch-pack: prepare for threaded fetching of packfile URIs Patrick Steinhardt
2026-08-21 12:31 ` [PATCH 2/2] fetch-pack: allow parallelizing packfile URI fetches Patrick Steinhardt
2026-08-31 2:33 ` [PATCH 0/2] " Justin Tobler
2026-08-31 5:43 ` Patrick Steinhardt [this message]
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=apUUiv4SD0-W8QS3@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=tnyman@openai.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