From: Jeff King <peff@peff.net>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH 0/3] delta-island fixes
Date: Thu, 22 Nov 2018 11:43:18 -0500 [thread overview]
Message-ID: <20181122164318.GG28192@sigill.intra.peff.net> (raw)
In-Reply-To: <778f1fcb-8988-de42-8264-d4394ede8540@gmail.com>
On Tue, Nov 20, 2018 at 10:06:57AM -0500, Derrick Stolee wrote:
> On 11/20/2018 4:44 AM, Jeff King wrote:
> > In cases like this I think it's often a good idea to have a perf test.
> > Those are expensive anyway, and we'd have the double benefit of
> > exercising the code and showing off the performance improvement. But the
> > delta-island code only makes sense on a very specialized repo: one where
> > you have multiple related but diverging histories. You could simulate
> > that by picking two branches in a repository, but the effect is going to
> > be miniscule.
>
> The changes in this series look correct. Too bad it is difficult to test.
>
> Perhaps we should add a performance test for the --delta-islands check that
> would trigger the failure (and maybe a clone afterwards). There are lots of
> freely available forks of git.git that present interesting fork structure.
> Here are three that would suffice to make this interesting:
>
> https://github.com/git/git
> https://github.com/git-for-windows/git
> https://github.com/microsoft/git
>
> Of course, running it on a specific repo is up to the person running the
> perf suite.
I hadn't really considered the possibility of reconstructing a fork
network repository from public repos. It probably would be possible to
include a script which does so, although:
- I suspect it's going to be pretty expensive. We can use --reference
to reduce the size of subsequent clones, but just the repacks you
have to do to assemble the final shared repo can get pretty
expensive.
- That's 3 forks. Our real-world case has over 4000. I'm not sure of
the size of the effects for smaller cases.
So in short, I think it's an interesting avenue to explore, but it might
turn out to be a dead-end. I'm not going to prioritize it right now, but
if somebody wants to play with it, I'd be happy to look over the
results.
-Peff
prev parent reply other threads:[~2018-11-22 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 9:44 [PATCH 0/3] delta-island fixes Jeff King
2018-11-20 9:46 ` [PATCH 1/3] pack-objects: fix tree_depth and layer invariants Jeff King
2018-11-20 16:37 ` Duy Nguyen
2018-11-22 16:50 ` Jeff King
2018-11-21 4:52 ` Junio C Hamano
2018-11-20 9:48 ` [PATCH 2/3] pack-objects: zero-initialize tree_depth/layer arrays Jeff King
2018-11-20 9:50 ` [PATCH 3/3] pack-objects: fix off-by-one in delta-island tree-depth computation Jeff King
2018-11-20 15:06 ` [PATCH 0/3] delta-island fixes Derrick Stolee
2018-11-22 16:43 ` Jeff King [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181122164318.GG28192@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=stolee@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).