From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: David Lang <david@lang.hm>,
Koosha Khajehmoogahi <koosha.khajeh@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Multi-threaded 'git clone'
Date: Mon, 16 Feb 2015 10:43:47 -0800 [thread overview]
Message-ID: <xmqq1tlp7l3w.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150216154745.GA10120@peff.net> (Jeff King's message of "Mon, 16 Feb 2015 10:47:45 -0500")
Jeff King <peff@peff.net> writes:
> ... And the whole output is checksummed by a single sha1
> over the whole stream that comes at the end.
>
> I think the most feasible thing would be to quickly spool it to a
> server on the LAN, and then use an existing fetch-in-parallel tool
> to grab it from there over the WAN.
One possibility would be for the server to prepare a static bundle
file to bootstrap all the "clone" clients with and publish it on a
CDN. A protocol extension would tell the client where to download
the bundle from, the client can then grab the bundle to clone from
it to become "slightly stale but mostly up to date", and then do a
usual incremental update with the server after that to be complete.
The server would update the bundle used to bootstrap clone clients
periodically in order to keep the incrementals to the minimum, and
would make sure their bitmap is anchored at the tips of bundles to
minimize the object counting load during the incremental phase.
I think "repo" used by folks who do AOSP does something similar to
that by scripting around "git clone". I'd imagine that they would
be happy to see if "git clone" did all that inside.
next prev parent reply other threads:[~2015-02-16 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 13:16 Multi-threaded 'git clone' Koosha Khajehmoogahi
2015-02-16 13:31 ` David Lang
2015-02-16 15:03 ` Jeff King
2015-02-16 15:31 ` David Lang
2015-02-16 15:47 ` Jeff King
2015-02-16 18:43 ` Junio C Hamano [this message]
2015-02-17 3:16 ` Shawn Pearce
2015-02-16 23:16 ` Duy Nguyen
2015-02-17 0:56 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2015-02-17 5:20 Martin Fick
2015-02-17 23:32 ` Junio C Hamano
2015-02-18 3:14 ` 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=xmqq1tlp7l3w.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=koosha.khajeh@gmail.com \
--cc=peff@peff.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.