From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Git packs friendly to block-level deduplication
Date: Wed, 24 Jan 2018 19:10:15 -0500 [thread overview]
Message-ID: <20180125001015.GA17856@sigill.intra.peff.net> (raw)
In-Reply-To: <87607qyfci.fsf@evledraar.gmail.com>
On Thu, Jan 25, 2018 at 01:03:25AM +0100, Ævar Arnfjörð Bjarmason wrote:
> > You may also want to use "--threads=1" to avoid non-determinism in the
> > generated packs. In theory, both repos would then produce identical base
> > packs, though it does not seem to do so in practice (I didn't dig in to
> > what the different may be).
>
> ..and north of 20% with --threads=1.
>
> [...]
>
> Thanks. I'll look into that, although the above results (sans hacking on
> the core pack-objects logic) suggest that even once I create an island
> I'm getting at most 20%.
I think it may be worth figuring out where the two differ. With
--no-reuse-object and --no-reuse-delta, I'd think that the pack
generated for a particular apex commit would be totally deterministic,
regardless of other objects available in the repo. But it's not for some
reason.
-Peff
next prev parent reply other threads:[~2018-01-25 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 22:03 Git packs friendly to block-level deduplication Ævar Arnfjörð Bjarmason
2018-01-24 22:19 ` Mike Hommey
2018-01-24 22:23 ` Junio C Hamano
2018-01-24 22:30 ` Mike Hommey
2018-01-24 22:47 ` Ævar Arnfjörð Bjarmason
2018-01-24 22:25 ` Eric Wong
2018-01-24 22:37 ` Elijah Newren
2018-01-24 23:06 ` Ævar Arnfjörð Bjarmason
2018-01-24 23:32 ` Jeff King
2018-01-24 23:22 ` Jeff King
2018-01-25 0:03 ` Ævar Arnfjörð Bjarmason
2018-01-25 0:10 ` Jeff King [this message]
2018-01-25 0:29 ` Jeff King
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=20180125001015.GA17856@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).