All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jon Simons <jon@jonsimons.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 09/12] remote: use strmap for match_explicit_refs()
Date: Thu, 05 Nov 2026 14:41:08 -0800	[thread overview]
Message-ID: <xmqqmrrmq4u3.fsf@gitster.g> (raw)
In-Reply-To: <20261014031347.50433-10-jon@jonsimons.org> (Jon Simons's message of "Tue, 13 Oct 2026 23:13:44 -0400")

Jon Simons <jon@jonsimons.org> writes:

> Optimize match_explicit_refs() by replacing two linear refs traversals
> with strmap lookups.

Ahh, an obvious thing to do for performance.  And the ...

>
> Before this change, matching R explicit refspecs against N local refs
> and M remote refs in match_explicit() entails O(R * N) and O(R * M)
> calls to refname_match() for sources and destinations respectively.
>
> After this change, we build a strmap for local refs O(N), a strmap for
> remote refs O(M), and use them for O(R * rules) lookups of the refspecs.
>
> Refspecs are resolved using count_refspec_match_in_map() introduced
> earlier in the series, which issues one strmap lookup for each candidate
> rules pattern generated with expand_ref_prefix().
>
> The match_explicit_lhs_map() function introduced in a previous commit
> has now been recombined into match_explicit_lhs(): all call sites are
> now using the new strmap variation.
>
> Timings show benefit where one or both of the client and remote have
> many refs, and multiple refspecs are specified:
>
>   Test                           HEAD~1            HEAD
>   -----------------------------------------------------------------------
>   5516.3: empty:refspecs:1       0.13(0.07+0.10)   0.14(0.07+0.10) +7.7%
>   5516.5: empty:refspecs:10      0.17(0.10+0.11)   0.14(0.07+0.11) -17.6%
>   5516.7: empty:refspecs:100     0.47(0.41+0.10)   0.15(0.08+0.10) -68.1%
>   5516.9: mirror:refspecs:1      0.17(0.10+0.11)   0.17(0.10+0.11) +0.0%
>   5516.11: mirror:refspecs:10    0.23(0.16+0.11)   0.17(0.10+0.11) -26.1%
>   5516.13: mirror:refspecs:100   0.87(0.80+0.11)   0.18(0.11+0.11) -79.3%

... numbers do look promising.

> -static int match_explicit_lhs_count(const int count,
> -				    struct refspec_item *rs,
> -				    struct ref **match,
> -				    int *allocated_match)
> +static int match_explicit_lhs(struct strmap *src,
> +			      struct refspec_item *rs,
> +			      struct ref **match,
> +			      int *allocated_match)
>  {
> -	switch (count) {
> +	switch (count_refspec_match_in_map(rs->src, src, match)) {
>  	case 1:
>  		if (allocated_match)
>  			*allocated_match = 0;
> @@ -1239,24 +1239,6 @@ static int match_explicit_lhs_count(const int count,
>  	}
>  }
>  
> -static int match_explicit_lhs(struct ref *src,
> -			      struct refspec_item *rs,
> -			      struct ref **match,
> -			      int *allocated_match)
> -{
> -	return match_explicit_lhs_count(count_refspec_match(rs->src, src, match),
> -					rs, match, allocated_match);
> -}

It is a bit unsatisfactory that we lose the callers to the linear
count_refspec_match() in this file, but still need to retain the
function itself for external callers.  It may be outside the scope
of this series, but are these external callers also benefit from
having access to the _in_map() variant (which would probably need to
expose not just that function but the ref_map_init() machinery)?


  reply	other threads:[~2026-11-05 22:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 19:29 [PATCH 00/15] push: speed up client-side refspec matching Jon Simons
2026-10-09 19:29 ` [PATCH 01/15] remote: validate --force-with-lease <refname> argument Jon Simons
2026-10-09 19:29 ` [PATCH 02/15] t5516: demonstrate push with "./"-prefixed source Jon Simons
2026-10-09 19:29 ` [PATCH 03/15] t5510: document fetch with "./"-prefixed branch.<name>.merge Jon Simons
2026-10-09 19:29 ` [PATCH 04/15] t/perf: add explicit delete refspec matching test Jon Simons
2026-10-09 19:29 ` [PATCH 05/15] refs: stop using mkpath() in refname_match() Jon Simons
2026-10-09 19:29 ` [PATCH 06/15] remote: use strmap for check_push_refs() Jon Simons
2026-10-09 19:29 ` [PATCH 07/15] t5516: test pushing two refspecs creating the same new branch Jon Simons
2026-10-09 19:29 ` [PATCH 08/15] t5408, t5410: test duplicate updates without relying on the client Jon Simons
2026-10-09 19:29 ` [PATCH 09/15] t5408: check refspec order with distinct destinations Jon Simons
2026-10-09 19:29 ` [PATCH 10/15] t5408: expect client-side error for duplicate destinations Jon Simons
2026-10-09 19:29 ` [PATCH 11/15] remote: reject duplicate destinations on an empty remote Jon Simons
2026-10-09 19:29 ` [PATCH 12/15] remote: use strmap for match_explicit_refs() Jon Simons
2026-10-09 19:29 ` [PATCH 13/15] t/perf: measure --force-with-lease in p5516 Jon Simons
2026-10-09 19:29 ` [PATCH 14/15] remote: restructure apply_push_cas() loops Jon Simons
2026-10-09 19:29 ` [PATCH 15/15] remote: use strmap for apply_push_cas() Jon Simons
2026-10-09 20:18 ` [PATCH 00/15] push: speed up client-side refspec matching Kristoffer Haugsbakk
2026-10-11  2:35   ` Jon Simons
2026-10-14  3:13 ` [PATCH v2 00/12] " Jon Simons
2026-10-14  3:13   ` [PATCH v2 01/12] remote: validate --force-with-lease <refname> argument Jon Simons
2026-11-05 23:03     ` Junio C Hamano
2026-10-14  3:13   ` [PATCH v2 02/12] t/perf: add explicit delete refspec matching test Jon Simons
2026-10-14  3:13   ` [PATCH v2 03/12] refs: stop using mkpath() in refname_match() Jon Simons
2026-10-28 21:19     ` SZEDER Gábor
2026-11-05 22:26     ` Junio C Hamano
2026-10-14  3:13   ` [PATCH v2 04/12] remote: use strmap for check_push_refs() Jon Simons
2026-10-14  3:13   ` [PATCH v2 05/12] send-pack: plug leak upon match_push_refs failure Jon Simons
2026-11-05 22:28     ` Junio C Hamano
2026-10-14  3:13   ` [PATCH v2 06/12] t5408, t5410: test duplicate updates without relying on the client Jon Simons
2026-10-14  3:13   ` [PATCH v2 07/12] t5408: check refspec order with distinct destinations Jon Simons
2026-10-14  3:13   ` [PATCH v2 08/12] remote: reject duplicate destinations on an empty remote Jon Simons
2026-11-05 22:32     ` Junio C Hamano
2026-10-14  3:13   ` [PATCH v2 09/12] remote: use strmap for match_explicit_refs() Jon Simons
2026-11-05 22:41     ` Junio C Hamano [this message]
2026-10-14  3:13   ` [PATCH v2 10/12] t/perf: measure --force-with-lease in p5516 Jon Simons
2026-10-14  3:13   ` [PATCH v2 11/12] remote: restructure apply_push_cas() loops Jon Simons
2026-10-14  3:13   ` [PATCH v2 12/12] remote: use strmap for apply_push_cas() Jon Simons
2026-11-05 22:49     ` Junio C Hamano

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=xmqqmrrmq4u3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jon@jonsimons.org \
    /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.