From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: szeder.dev@gmail.com, avarab@gmail.com,
abhishekkumar8222@gmail.com, me@ttaylorr.com,
Derrick Stolee <dstolee@microsoft.com>
Subject: [PATCH 0/2] Accelerate "git merge-base --is-ancestor"
Date: Wed, 17 Jun 2020 17:24:27 +0000 [thread overview]
Message-ID: <pull.664.git.1592414670.gitgitgadget@gmail.com> (raw)
It was recently [1] reported (and not-so-recently [2] reported) that "git
merge-base --is-ancestor" can be pretty slow. In fact, it is regularly
slower than "git branch --contains" or "git tag --contains", which are
answering a "harder" query.
[1] https://lore.kernel.org/git/20200607195347.GA8232@szeder.dev/
[2] https://lore.kernel.org/git/87608bawoa.fsf@evledraar.gmail.com/
The root cause is that the in_merge_base() implementation is skipping the
fast can_all_from_reach() implementation and using paint_down_to_common()
instead. Note that these are equivalent: a commit A is in the set of
merge-bases between A and B if and only if B can reach A.
This fixes the issue, and makes the performance degradation reported by
Szeder a non-issue.
Thanks, -Stolee
Derrick Stolee (2):
commit-reach: create repo_is_descendant_of()
commit-reach: use fast logic in repo_in_merge_base
commit-reach.c | 21 ++++++++++++++++++---
1 file changed, 18 insertions(+), 3 deletions(-)
base-commit: b3d7a52fac39193503a0b6728771d1bf6a161464
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-664%2Fderrickstolee%2Fmerge-base-is-ancestor-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-664/derrickstolee/merge-base-is-ancestor-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/664
--
gitgitgadget
next reply other threads:[~2020-06-17 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 17:24 Derrick Stolee via GitGitGadget [this message]
2020-06-17 17:24 ` [PATCH 1/2] commit-reach: create repo_is_descendant_of() Derrick Stolee via GitGitGadget
2020-06-29 13:40 ` Taylor Blau
2020-06-30 1:45 ` Derrick Stolee
2020-06-17 17:24 ` [PATCH 2/2] commit-reach: use fast logic in repo_in_merge_base Derrick Stolee via GitGitGadget
2020-06-17 20:46 ` [PATCH 0/2] Accelerate "git merge-base --is-ancestor" Junio C Hamano
2020-06-18 1:37 ` Derrick Stolee
2020-06-19 6:10 ` Abhishek Kumar
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=pull.664.git.1592414670.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=abhishekkumar8222@gmail.com \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.
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.