Re: Sensible way to see what objects are being fetched just-in-time in a partial clone?

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 26, 2024, 17:28 UTC
Message-ID: <xmqqv7znjir3.fsf@gitster.g>
In-Reply-To: <CAPMMpog7=ZnhJhrgZFwzRZibLtK1-LyOhsrp5c4O85ocRFDZxw@mail.gmail.com>

Tao Klerks <tao@klerks.biz> writes:

Show 6 quoted lines

> This was a sucky process though - and I was very surprised that I
> couldn't see what was being fetched (what the stdin content to the
> just-in-time fetch calls were) with any of the trace env vars that I
> was able to find documented: GIT_TRACE, GIT_CURL_VERBOSE,
> GIT_TRACE_PERFORMANCE, GIT_TRACE_PACK_ACCESS, GIT_TRACE_PACKET,
> GIT_TRACE_PACKFILE, GIT_TRACE_SETUP, GIT_TRACE_SHALLOW

Yeah, lazy fetch codepath seems to be, eh, not quite well polished yet.

I am kind of surprised that there is no trace2() events around promisor_remote_get_direct() or its callers. Perhaps it is a good idea to add one to log how often it is triggered, and how large a batch the callers of the function is making?

Unlike the diff machinery, blame does not have a prefetch machinery. I am glad that somebody is looking at it.