From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/3] git-fetch: test avoiding unnecessary copying from alternates
Date: Thu, 8 Nov 2007 03:34:40 -0500 [thread overview]
Message-ID: <20071108083440.GK14735@spearce.org> (raw)
In-Reply-To: <20071108082213.GA17054@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> wrote:
> This test verifies my prior "avoid local fetching from alternate"
> patch is functional and doesn't regress in the future during any
> additional improvements made to git.
...
> +test_expect_success 'quickfetch should not copy from alternate' '
> +
> + (
> + mkdir quickclone &&
> + cd quickclone &&
> + git init-db &&
> + (cd ../.git/objects && pwd) >.git/objects/info/alternates &&
> + git remote add origin .. &&
> + git fetch -k -k
Hmmph. On second thought I think this is a little sketchy for
a test. Versions without my quickfetch patch fail this test and
versions with it pass. But it depends on the implementation of
`-k -k` to always call index-pack over unpack-objects.
I'm using -k -k here to ensure we keep the pack fetched as we're only
fetching 6 objects and they are already reachable in the quickclone
repository thanks to the alternate ODB. If we use unpack-objects
during this fetch we will still pass this test because the objects
won't be unpacked if they are already reachable locally.
Of course this test is for a performance optimization. For 6
tiny objects it really doesn't matter if we copy them or not, or
if we copy them over a pipe only to discard them because they are
already reachable. It does however matter when you are talking
about nearly 300MB worth of objects. :-\
--
Shawn.
prev parent reply other threads:[~2007-11-08 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 8:22 [PATCH 4/3] git-fetch: test avoiding unnecessary copying from alternates Shawn O. Pearce
2007-11-08 8:34 ` Shawn O. Pearce [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=20071108083440.GK14735@spearce.org \
--to=spearce@spearce.org \
--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 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.