From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, peff@peff.net, chriscool@tuxfamily.org
Subject: Re: [PATCH 4/4] pack-bitmap: pass object filter to fill-in traversal
Date: Mon, 04 May 2020 22:40:43 -0700 [thread overview]
Message-ID: <xmqq1rnzc52c.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <f1eb194b9fdf5e385610fa3c0ddee22b89cf4f0e.1588633810.git.me@ttaylorr.com> (Taylor Blau's message of "Mon, 4 May 2020 17:12:38 -0600")
Taylor Blau <me@ttaylorr.com> writes:
> But now that we support tree filters, there's opportunity for savings. A
> tree:depth=0 filter means we can avoid accessing trees entirely, since
> we know we won't them (or any of the subtrees or blobs they point to).
"we know we won't _have_ them"?
> @@ -506,7 +506,8 @@ static int should_include(struct commit *commit, void *_data)
> static struct bitmap *find_objects(struct bitmap_index *bitmap_git,
> struct rev_info *revs,
> struct object_list *roots,
> - struct bitmap *seen)
> + struct bitmap *seen,
> + struct list_objects_filter_options *filter)
> {
> struct bitmap *base = NULL;
> int needs_walk = 0;
> @@ -599,8 +600,9 @@ static struct bitmap *find_objects(struct bitmap_index *bitmap_git,
> show_data.bitmap_git = bitmap_git;
> show_data.base = base;
>
> - traverse_commit_list(revs, show_commit, show_object,
> - &show_data);
> + traverse_commit_list_filtered(filter, revs,
> + show_commit, show_object,
> + &show_data, NULL);
And then finally the change in step 1/4 pays off.
> }
>
> return base;
> @@ -999,7 +1001,8 @@ struct bitmap_index *prepare_bitmap_walk(struct rev_info *revs,
>
> if (haves) {
> revs->ignore_missing_links = 1;
> - haves_bitmap = find_objects(bitmap_git, revs, haves, NULL);
> + haves_bitmap = find_objects(bitmap_git, revs, haves, NULL,
> + filter);
> reset_revision_walk();
> revs->ignore_missing_links = 0;
>
> @@ -1007,7 +1010,8 @@ struct bitmap_index *prepare_bitmap_walk(struct rev_info *revs,
> BUG("failed to perform bitmap walk");
> }
>
> - wants_bitmap = find_objects(bitmap_git, revs, wants, haves_bitmap);
> + wants_bitmap = find_objects(bitmap_git, revs, wants, haves_bitmap,
> + filter);
>
> if (!wants_bitmap)
> BUG("failed to perform bitmap walk");
> diff --git a/t/perf/p5310-pack-bitmaps.sh b/t/perf/p5310-pack-bitmaps.sh
> index 75ccf9f4e3..b3e725f031 100755
> --- a/t/perf/p5310-pack-bitmaps.sh
> +++ b/t/perf/p5310-pack-bitmaps.sh
> @@ -91,4 +91,9 @@ test_perf 'pack to file (partial bitmap)' '
> git pack-objects --use-bitmap-index --all pack2b </dev/null >/dev/null
> '
>
> +test_perf 'rev-list with tree filter (partial bitmap)' '
> + git rev-list --use-bitmap-index --count --objects --all \
> + --filter=tree:0 >/dev/null
> +'
> +
> test_done
next prev parent reply other threads:[~2020-05-05 5:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 23:12 [PATCH 0/4] pack-bitmap: use bitmaps for traversals with '--filter=tree:0' Taylor Blau
2020-05-04 23:12 ` [PATCH 1/4] list-objects-filter: treat NULL filter_options as "disabled" Taylor Blau
2020-05-05 5:07 ` Junio C Hamano
2020-05-04 23:12 ` [PATCH 2/4] pack-bitmap.c: make object filtering functions generic Taylor Blau
2020-05-05 5:12 ` Junio C Hamano
2020-05-04 23:12 ` [PATCH 3/4] pack-bitmap.c: support 'tree:0' filtering Taylor Blau
2020-05-05 5:25 ` Junio C Hamano
2020-05-05 15:59 ` Taylor Blau
2020-05-05 18:20 ` Junio C Hamano
2020-05-04 23:12 ` [PATCH 4/4] pack-bitmap: pass object filter to fill-in traversal Taylor Blau
2020-05-05 5:40 ` Junio C Hamano [this message]
2020-05-05 16:00 ` Taylor Blau
-- strict thread matches above, loose matches on Subject: below --
2020-04-22 23:13 [PATCH 0/4] pack-bitmap: use bitmaps for traversals with '--filter=tree:0' Taylor Blau
2020-04-22 23:13 ` [PATCH 4/4] pack-bitmap: pass object filter to fill-in traversal Taylor Blau
2020-04-24 5:42 ` Jeff King
2020-04-24 16:54 ` Taylor Blau
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=xmqq1rnzc52c.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.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.
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).