git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] bloom: ignore renames when computing changed paths

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 8, 2020, 19:11 UTC
Message-ID
<xmqqftddpzc4.fsf@gitster.c.googlers.com>
In-Reply-To
<pull.601.git.1586363907252.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 10 quoted lines
> From: Derrick Stolee <dstolee@microsoft.com>
>
> The changed-path Bloom filters record an entry in the filter for
> every path that was changed. This includes every add and delete,
> regardless of whther a rename was detected. Detecting renames
> causes significant performance issues, but also will trigger
> downloading missing blobs in partial clone.
>
> The simple fix is to disable rename detection when computing a
> changed-path Bloom filter.
Makes perfect sense to me.
Show 14 quoted lines
> diff --git a/bloom.c b/bloom.c
> index c5b461d1cfe..dd9bab9bbd6 100644
> --- a/bloom.c
> +++ b/bloom.c
> @@ -189,6 +189,7 @@ struct bloom_filter *get_bloom_filter(struct repository *r,
>  
>  	repo_diff_setup(r, &diffopt);
>  	diffopt.flags.recursive = 1;
> +	diffopt.detect_rename = 0;
>  	diffopt.max_changes = max_changes;
>  	diff_setup_done(&diffopt);
>  
>
> base-commit: d5b873c832d832e44523d1d2a9d29afe2b84c84f
Previous: Derrick Stolee via GitGitGadgetNext: Philip Oakley
Message 2 of 9 in “bloom: ignore renames when computing changed paths”
  1. bloom: ignore renames when computing changed pathsDerrick Stolee via GitGitGadget, Apr 8, 2020
  2. Junio C HamanoApr 8, 2020
  3. Philip OakleyApr 8, 2020
  4. Jeff KingApr 8, 2020
  5. Derrick StoleeApr 9, 2020
  6. Jeff KingApr 9, 2020
  7. Derrick StoleeApr 9, 2020
  8. Jeff KingApr 9, 2020
  9. bloom: ignore renames when computing changed pathsDerrick Stolee via GitGitGadget, Apr 9, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.