From: Junio C Hamano <gitster@pobox.com>
To: Arijit Banerjee <arijit91@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
"Arijit Banerjee via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Derrick Stolee" <stolee@gmail.com>,
"Arijit Banerjee" <arijit@effectiveailabs.com>
Subject: Re: [PATCH v3] index-pack: retain child bases in delta cache
Date: Wed, 10 Jun 2026 07:51:19 -0700 [thread overview]
Message-ID: <xmqqldcmxxco.fsf@gitster.g> (raw)
In-Reply-To: <08B48BBE-4084-4619-94B0-503158B93BEF@gmail.com> (Arijit Banerjee's message of "Fri, 5 Jun 2026 14:18:27 -0700")
Arijit Banerjee <arijit91@gmail.com> writes:
> Apologies, my earlier replies were sent through GitHub's notification
> emails and appeared only as PR comments, so they did not reach the mailing
> list.
>
> On Thu, Jun 4, 2026, Jeff King wrote:
>> So I am happy with either v2 or v3.
>
> I also did not see a meaningful performance difference between v2 and v3.
> I am happy with either direction and defer to the maintainers on whether
> v3's more precise release is worth the added complexity.
I have no strong preference either way.
> On Wed, Jun 3, 2026, Derrick Stolee wrote:
>> Did you see any evidence that this change has the intended effect of
>> reducing process memory proactively instead of relying on cache evictions?
>
> I do not have strong RSS evidence. The spot checks showed no meaningful RSS
> change, and max RSS is not a good signal here because free_base_data()
> lowers Git's internal base_cache_used accounting but may not return pages
> to the OS or reduce the recorded peak.
>
> The evidence for v3 is therefore structural: it releases the cached data
> once all direct children have been dispatched and retain_data reaches zero,
> rather than waiting for cache-pressure eviction.
prev parent reply other threads:[~2026-06-10 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 16:06 [PATCH] index-pack: retain child bases in delta cache Arijit Banerjee via GitGitGadget
2026-06-01 12:50 ` Derrick Stolee
2026-06-01 16:13 ` [PATCH v2] " Arijit Banerjee via GitGitGadget
2026-06-02 6:45 ` Jeff King
2026-06-03 0:05 ` [PATCH v3] " Arijit Banerjee via GitGitGadget
2026-06-03 12:24 ` Derrick Stolee
2026-06-04 7:12 ` Jeff King
2026-06-05 21:18 ` Arijit Banerjee
2026-06-10 14:51 ` Junio C Hamano [this message]
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=xmqqldcmxxco.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=arijit91@gmail.com \
--cc=arijit@effectiveailabs.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--cc=stolee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox