From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: thin packs ending up fat
Date: Thu, 12 Jan 2012 20:51:17 -0500 [thread overview]
Message-ID: <20120113015117.GA8245@sigill.intra.peff.net> (raw)
In-Reply-To: <7vwr8wz8u9.fsf@alter.siamese.dyndns.org>
On Thu, Jan 12, 2012 at 05:31:42PM -0800, Junio C Hamano wrote:
> From: Jeff King <peff@peff.net>
> Subject: [PATCH] thin-pack: try harder to create delta against preferred base
I just sat down to write a nicer commit message, and behold, it was done
for me. Thanks.
> When creating a thin-pack to transfer recent history, it is likely that we
> will try to send an object that is recorded in full, as it is newer. But
> the heuristics to avoid recomputing futile delta effectively forbids us
> from attempting to express such an object as a delta based on another
> object. Sending an object in full is often more expensive than sending a
> suboptimal delta based on other objects, and it is even more so if we
> could use an object we know the receiving end already has (i.e. referred
> base object) as the delta base.
s/referred/preferred/
> Tweak the recomputation avoidance logic, so that we do not punt on
> computing delta against a preferred base object.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Other than that, it looks good to me.
Signed-off-by: Jeff King <peff@peff.net>
I'll try to deploy this to GitHub in the near future. I doubt we'll see
much of a dent in our bandwidth, though, as small fetches that this
helps are probably lost in the noise of clones.
-Peff
next prev parent reply other threads:[~2012-01-13 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 22:15 thin packs ending up fat Jeff King
2012-01-12 22:32 ` Jeff King
2012-01-12 23:54 ` Nicolas Pitre
2012-01-13 0:14 ` Junio C Hamano
2012-01-13 1:31 ` Junio C Hamano
2012-01-13 1:51 ` Jeff King [this message]
2012-01-13 1:59 ` Jeff King
2012-01-13 7:19 ` Junio C Hamano
2012-01-13 15:15 ` Jeff King
2012-01-13 2:19 ` Nicolas Pitre
2012-01-13 8:28 ` Ævar Arnfjörð Bjarmason
2012-01-13 15:55 ` 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=20120113015117.GA8245@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.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 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).