From: Jeff King <peff@peff.net>
To: Duy Nguyen <pclouds@gmail.com>
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 19:56:32 -0500 [thread overview]
Message-ID: <20150217005632.GA13001@peff.net> (raw)
In-Reply-To: <CACsJy8Brnu7rBxtCq_ac58BW7dOK=wtzMxVL-gsOUXJB2Jss9w@mail.gmail.com>
On Tue, Feb 17, 2015 at 06:16:39AM +0700, Duy Nguyen wrote:
> On Mon, Feb 16, 2015 at 10:47 PM, Jeff King <peff@peff.net> wrote:
> > Each clone generates the pack on the fly
> > based on what's on disk and streams it out. It should _usually_ be the
> > same, but there's nothing to guarantee byte-for-byte equality between
> > invocations.
>
> It's usually _not_ the same. I tried when I wanted to produce stable
> packs. The first condition is single-threaded pack-objects. Otherwise
> thread scheduler could make object order unpredictable.
True. If you keep your server repositories fully packed, that eliminates
the delta search (and/or makes it feasible to turn pack.threads to 1 to
make it deterministic). But any change in the repository (e.g., somebody
else pushing, even to a ref you are not fetching) can cause unexpected
changes in the bytes.
-Peff
next prev parent reply other threads:[~2015-02-17 0:56 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
2015-02-17 3:16 ` Shawn Pearce
2015-02-16 23:16 ` Duy Nguyen
2015-02-17 0:56 ` Jeff King [this message]
-- 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=20150217005632.GA13001@peff.net \
--to=peff@peff.net \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=koosha.khajeh@gmail.com \
--cc=pclouds@gmail.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;
as well as URLs for NNTP newsgroup(s).