From: Taylor Blau <me@ttaylorr.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "SZEDER Gábor via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, szeder.dev@gmail.com,
"Derrick Stolee" <dstolee@microsoft.com>
Subject: Re: [PATCH 5/8] commit-graph: check all leading directories in changed path Bloom filters
Date: Fri, 19 Jun 2020 11:19:22 -0600 [thread overview]
Message-ID: <20200619171922.GA57283@syl.local> (raw)
In-Reply-To: <20200619171717.GA55911@syl.local>
On Fri, Jun 19, 2020 at 11:17:17AM -0600, Taylor Blau wrote:
> Hi Stolee,
>
> On Mon, Jun 15, 2020 at 08:14:50PM +0000, SZEDER Gábor via GitGitGadget wrote:
> > From: =?UTF-8?q?SZEDER=20G=C3=A1bor?= <szeder.dev@gmail.com>
> >
> > The file 'dir/subdir/file' can only be modified if its leading
> > directories 'dir' and 'dir/subdir' are modified as well.
> >
> > So when checking modified path Bloom filters looking for commits
> > modifying a path with multiple path components, then check not only
> > the full path in the Bloom filters, but all its leading directories as
> > well. Take care to check these paths in "deepest first" order,
> > because it's the full path that is least likely to be modified, and
> > the Bloom filter queries can short circuit sooner.
> >
> > This can significantly reduce the average false positive rate, by
> > about an order of magnitude or three(!), and can further speed up
> > pathspec-limited revision walks. The table below compares the average
> > false positive rate and runtime of
> >
> > git rev-list HEAD -- "$path"
> >
> > before and after this change for 5000+ randomly* selected paths from
> > each repository:
> >
> > Average false Average Average
> > positive rate runtime runtime
> > before after before after difference
> > ------------------------------------------------------------------
> > git 3.220% 0.7853% 0.0558s 0.0387s -30.6%
> > linux 2.453% 0.0296% 0.1046s 0.0766s -26.8%
> > tensorflow 2.536% 0.6977% 0.0594s 0.0420s -29.2%
> >
> > *Path selection was done with the following pipeline:
> >
> > git ls-tree -r --name-only HEAD | sort -R | head -n 5000
> >
> > The improvements in runtime are much smaller than the improvements in
> > average false positive rate, as we are clearly reaching diminishing
> > returns here. However, all these timings depend on that accessing
> > tree objects is reasonably fast (warm caches). If we had a partial
> > clone and the tree objects had to be fetched from a promisor remote,
> > e.g.:
> >
> > $ git clone --filter=tree:0 --bare file://.../webkit.git webkit.notrees.git
> > $ git -C webkit.git -c core.modifiedPathBloomFilters=1 \
> > commit-graph write --reachable
> > $ cp webkit.git/objects/info/commit-graph webkit.notrees.git/objects/info/
> > $ git -C webkit.notrees.git -c core.modifiedPathBloomFilters=1 \
> > rev-list HEAD -- "$path"
> >
> > then checking all leading path component can reduce the runtime from
> > over an hour to a few seconds (and this is with the clone and the
> > promisor on the same machine).
> >
> > This adjusts the tracing values in t4216-log-bloom.sh, which provides a
> > concrete way to notice the improvement.
> >
> > Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
> > Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
> > ---
> > revision.c | 35 ++++++++++++++++++++++++++---------
> > revision.h | 6 ++++--
> > t/t4216-log-bloom.sh | 2 +-
> > 3 files changed, 31 insertions(+), 12 deletions(-)
> >
> > diff --git a/revision.c b/revision.c
> > index c644c660917..027ae3982b4 100644
> > --- a/revision.c
> > +++ b/revision.c
> > @@ -670,9 +670,10 @@ static void prepare_to_use_bloom_filter(struct rev_info *revs)
> > {
> > struct pathspec_item *pi;
> > char *path_alloc = NULL;
> > - const char *path;
> > + const char *path, *p;
> > int last_index;
> > - int len;
> > + size_t len;
> > + int path_component_nr = 0, j;
> >
> > if (!revs->commits)
> > return;
> > @@ -705,8 +706,22 @@ static void prepare_to_use_bloom_filter(struct rev_info *revs)
> >
> > len = strlen(path);
> >
> > - revs->bloom_key = xmalloc(sizeof(struct bloom_key));
> > - fill_bloom_key(path, len, revs->bloom_key, revs->bloom_filter_settings);
> > + p = path;
> > + do {
> > + p = strchrnul(p + 1, '/');
> > + path_component_nr++;
> > + } while (p - path < len);
> > +
> > + revs->bloom_keys_nr = path_component_nr;
> > + ALLOC_ARRAY(revs->bloom_keys, revs->bloom_keys_nr);
> > +
> > + p = path;
> > + for (j = 0; j < revs->bloom_keys_nr; j++) {
> > + p = strchrnul(p + 1, '/');
> > +
> > + fill_bloom_key(path, p - path, &revs->bloom_keys[j],
> > + revs->bloom_filter_settings);
> > + }
> >
>
> Somewhat related to our off-list discussion yesterday, there is a bug in
> both 2.27 and this patch which produces incorrect results when (1)
> Bloom filters are enabled, and (2) we are doing a revision walk from
> root with the pathspec '.'.
>
> What appears to be going on is that our normalization takes '.' -> '',
> and then we form a Bloom key based on the empty string, which will
> return 'definitely not' when querying the Bloom filter some of the time,
> which should never happen. This is a consequence of never inserting the
> empty key into the Bloom filter upon generation.
>
> As a result, I have patched this in GitHub's fork (which is currently
> based on 2.27 and doesn't have these patches yet) by doing an early
> return when 'strlen(path) == 0'. Since it looks like these patches are
> going to land, here is some clean-up and a fix for the bug that you
> should feel free to test with and apply on top:
>
> --- >8 ---
>
> diff --git a/revision.c b/revision.c
> index 8bd383b1dd..123e72698d 100644
> --- a/revision.c
> +++ b/revision.c
> @@ -670,10 +670,10 @@ static void prepare_to_use_bloom_filter(struct rev_info *revs)
> {
> struct pathspec_item *pi;
> char *path_alloc = NULL;
> - const char *path, *p;
> + char *path, *p;
> int last_index;
> size_t len;
> - int path_component_nr = 0, j;
> + int path_component_nr = 1, j;
>
> if (!revs->commits)
> return;
> @@ -698,29 +698,33 @@ static void prepare_to_use_bloom_filter(struct rev_info *revs)
>
> /* remove single trailing slash from path, if needed */
> if (pi->match[last_index] == '/') {
> - path_alloc = xstrdup(pi->match);
> - path_alloc[last_index] = '\0';
> - path = path_alloc;
> - } else
> - path = pi->match;
> + path_alloc = xstrdup(pi->match);
> + path_alloc[last_index] = '\0';
> + path = path_alloc;
> + } else {
> + path = pi->match;
> + len = pi->len;
> + }
>
> - len = strlen(path);
> + if (!len)
> + return;
I should note that _this_ is the critical fix, and it should fix the bug
if you only applied just this hunk.
Everything else is purely style clean-ups on top (ranging from the four
spaces used instead of a tab, to some string processing niceties that I
_think_ should address Rene's concern, although I'm not sure if an
actual bug is lurking there or not...)
> - p = path;
> do {
> - p = strchrnul(p + 1, '/');
> - path_component_nr++;
> - } while (p - path < len);
> + if (is_dir_sep(*p)) {
> + *p = '\0';
> + path_component_nr++;
> + }
> + } while (*p++);
>
> revs->bloom_keys_nr = path_component_nr;
> ALLOC_ARRAY(revs->bloom_keys, revs->bloom_keys_nr);
>
> p = path;
> for (j = 0; j < revs->bloom_keys_nr; j++) {
> - p = strchrnul(p + 1, '/');
> -
> - fill_bloom_key(path, p - path, &revs->bloom_keys[j],
> + size_t plen = strlen(p);
> + fill_bloom_key(p, plen, &revs->bloom_keys[j],
> revs->bloom_filter_settings);
> + p += plen;
> }
>
> if (trace2_is_enabled() && !bloom_filter_atexit_registered) {
>
> > if (trace2_is_enabled() && !bloom_filter_atexit_registered) {
> > atexit(trace2_bloom_filter_statistics_atexit);
> > @@ -720,7 +735,7 @@ static int check_maybe_different_in_bloom_filter(struct rev_info *revs,
> > struct commit *commit)
> > {
> > struct bloom_filter *filter;
> > - int result;
> > + int result = 1, j;
> >
> > if (!revs->repo->objects->commit_graph)
> > return -1;
> > @@ -740,9 +755,11 @@ static int check_maybe_different_in_bloom_filter(struct rev_info *revs,
> > return -1;
> > }
> >
> > - result = bloom_filter_contains(filter,
> > - revs->bloom_key,
> > - revs->bloom_filter_settings);
> > + for (j = 0; result && j < revs->bloom_keys_nr; j++) {
> > + result = bloom_filter_contains(filter,
> > + &revs->bloom_keys[j],
> > + revs->bloom_filter_settings);
> > + }
> >
> > if (result)
> > count_bloom_filter_maybe++;
> > @@ -782,7 +799,7 @@ static int rev_compare_tree(struct rev_info *revs,
> > return REV_TREE_SAME;
> > }
> >
> > - if (revs->bloom_key && !nth_parent) {
> > + if (revs->bloom_keys_nr && !nth_parent) {
> > bloom_ret = check_maybe_different_in_bloom_filter(revs, commit);
> >
> > if (bloom_ret == 0)
> > diff --git a/revision.h b/revision.h
> > index 7c026fe41fc..abbfb4ab59a 100644
> > --- a/revision.h
> > +++ b/revision.h
> > @@ -295,8 +295,10 @@ struct rev_info {
> > struct topo_walk_info *topo_walk_info;
> >
> > /* Commit graph bloom filter fields */
> > - /* The bloom filter key for the pathspec */
> > - struct bloom_key *bloom_key;
> > + /* The bloom filter key(s) for the pathspec */
> > + struct bloom_key *bloom_keys;
> > + int bloom_keys_nr;
> > +
> > /*
> > * The bloom filter settings used to generate the key.
> > * This is loaded from the commit-graph being used.
> > diff --git a/t/t4216-log-bloom.sh b/t/t4216-log-bloom.sh
> > index c7011f33e2c..c13b97d3bda 100755
> > --- a/t/t4216-log-bloom.sh
> > +++ b/t/t4216-log-bloom.sh
> > @@ -142,7 +142,7 @@ test_expect_success 'setup - add commit-graph to the chain with Bloom filters' '
> >
> > test_bloom_filters_used_when_some_filters_are_missing () {
> > log_args=$1
> > - bloom_trace_prefix="statistics:{\"filter_not_present\":3,\"zero_length_filter\":0,\"maybe\":8,\"definitely_not\":6"
> > + bloom_trace_prefix="statistics:{\"filter_not_present\":3,\"zero_length_filter\":0,\"maybe\":6,\"definitely_not\":8"
> > setup "$log_args" &&
> > grep -q "$bloom_trace_prefix" "$TRASH_DIRECTORY/trace.perf" &&
> > test_cmp log_wo_bloom log_w_bloom
> > --
> > gitgitgadget
> >
> Thanks,
> Taylor
Thanks,
Taylor
next prev parent reply other threads:[~2020-06-19 17:19 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:14 [PATCH 0/8] More commit-graph/Bloom filter improvements Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 1/8] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-19 12:58 ` Derrick Stolee
2020-06-15 20:14 ` [PATCH 2/8] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-15 20:14 ` [PATCH 3/8] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-15 20:14 ` [PATCH 4/8] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-15 20:14 ` [PATCH 5/8] commit-graph: check all leading directories in changed path Bloom filters SZEDER Gábor via GitGitGadget
2020-06-18 20:31 ` René Scharfe
2020-06-19 9:14 ` René Scharfe
2020-06-19 17:17 ` Taylor Blau
2020-06-19 17:19 ` Taylor Blau [this message]
2020-06-23 13:47 ` Derrick Stolee
2020-06-15 20:14 ` [PATCH 6/8] bloom: enforce a minimum size of 8 bytes Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 7/8] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 8/8] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-17 21:21 ` [PATCH 0/8] More commit-graph/Bloom filter improvements Junio C Hamano
2020-06-18 1:46 ` Derrick Stolee
2020-06-23 17:46 ` [PATCH v2 00/11] " Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 01/11] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 02/11] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 03/11] bloom: get_bloom_filter() cleanups Derrick Stolee via GitGitGadget
2020-06-25 7:24 ` René Scharfe
2020-06-23 17:47 ` [PATCH v2 04/11] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 05/11] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-23 17:47 ` [PATCH v2 06/11] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 14:59 ` Derrick Stolee
2020-06-23 17:47 ` [PATCH v2 07/11] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 15:02 ` Derrick Stolee
2020-06-23 17:47 ` [PATCH v2 08/11] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 09/11] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 10/11] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 15:05 ` Derrick Stolee
2020-06-26 6:34 ` SZEDER Gábor
2020-06-26 14:42 ` Derrick Stolee
2020-06-23 17:47 ` [PATCH v2 11/11] bloom: enforce a minimum size of 8 bytes Derrick Stolee via GitGitGadget
2020-06-24 23:11 ` [PATCH v2 00/11] More commit-graph/Bloom filter improvements Junio C Hamano
2020-06-24 23:32 ` Derrick Stolee
2020-06-25 0:38 ` Junio C Hamano
2020-06-25 13:38 ` Derrick Stolee
2020-06-25 16:34 ` Junio C Hamano
2020-06-26 12:30 ` [PATCH v3 00/10] " Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 01/10] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 02/10] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 03/10] bloom: fix logic in get_bloom_filter() Derrick Stolee via GitGitGadget
2020-06-27 16:33 ` SZEDER Gábor
2020-06-29 13:02 ` Derrick Stolee
2020-06-26 12:30 ` [PATCH v3 04/10] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 05/10] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 06/10] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 07/10] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 08/10] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 09/10] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 10/10] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 00/10] More commit-graph/Bloom filter improvements Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 01/10] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 02/10] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 03/10] bloom: fix logic in get_bloom_filter() Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 04/10] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-10-15 13:21 ` SZEDER Gábor
2020-10-15 21:41 ` Taylor Blau
2020-10-16 2:18 ` Derrick Stolee
2020-10-16 3:18 ` Taylor Blau
2020-10-16 13:52 ` Derrick Stolee
2020-07-01 13:27 ` [PATCH v4 05/10] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 06/10] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 07/10] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 08/10] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 09/10] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 10/10] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
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=20200619171922.GA57283@syl.local \
--to=me@ttaylorr.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=szeder.dev@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).