git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: Patrick Steinhardt <ps@pks.im>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] commit: avoid parent list buildup in clear_commit_marks_many()
Date: Sun, 23 Feb 2025 09:25:54 +0100	[thread overview]
Message-ID: <a5be80b2-bcc0-400d-8f83-f537a71d83a4@web.de> (raw)
In-Reply-To: <Z7LYI4tqGZzZ2Vaw@pks.im>

Am 17.02.25 um 07:33 schrieb Patrick Steinhardt:
> On Thu, Feb 13, 2025 at 10:38:51PM +0100, René Scharfe wrote:
>> Am 12.02.25 um 08:05 schrieb Patrick Steinhardt:
>>
>> Well, the maximum list length for clear_commit_marks_many() calls with
>> nr > 1 in the test suite goes from 12 in t6600 to 4 with the patch.  Not
>> that exciting.  The question to me is: Why pile up parents in the list
>> when we can clean them earlier with no downside?  Or is there any?
>
> If it really is without downsides then yes, it's a nice improvement. I
> was mostly wondering whether you're fixing something where the old way
> of doing things performs _significantly_ worse and where the change
> could lead to a user-visible improvement. Like, requiring us to store
> orders of magnitudes less commits at the same time.

You could construct pathological cases, e.g., cleaning lots of disjoint
histories, but I don't expect any dramatic impact to real usage of the
function.  It's just a small improvement.

René


  reply	other threads:[~2025-02-23  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 10:41 [PATCH] commit: avoid parent list buildup in clear_commit_marks_many() René Scharfe
2025-02-12  7:05 ` Patrick Steinhardt
2025-02-13 21:38   ` René Scharfe
2025-02-17  6:33     ` Patrick Steinhardt
2025-02-23  8:25       ` René Scharfe [this message]
2025-02-23  8:26 ` [PATCH resend] " René Scharfe

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=a5be80b2-bcc0-400d-8f83-f537a71d83a4@web.de \
    --to=l.s.r@web.de \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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 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 NNTP newsgroup(s).