[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65720: [bug#66650] bug#65720: [bug#66650] [PATCH] git: Shell out to
From: |
Ludovic Courtès |
Subject: |
bug#65720: [bug#66650] bug#65720: [bug#66650] [PATCH] git: Shell out to ‘git gc’ when necessary. |
Date: |
Wed, 22 Nov 2023 12:17:55 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi,
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> On Thu, 16 Nov 2023 at 13:12, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> > Well, I expect “guix gc” to take some time and I choose when. However,
>> > I want “guix pull” or “guix time-machine” to be as fast as possible and
>> > here some extra time is added, and I cannot control exactly when.
>>
>> Yes, I see. The thing is ‘maybe-run-git-gc’ is only called on the slow
>> path; so for example, it’s not called on a ‘time-machine’ cache hit, but
>> only on a cache miss, which is already expensive anyway.
>
> What you mean as "only called on the slow path" is each time
> 'update-cached-checkout' is called, right?
Yes, which usually indicates we’re on a cache miss (for example a cache
miss of ‘guix time-machine’) and thus are going to do potentially more
work (updating a Git repo, building things, etc.). That’s why I think
it’s on the “slow path” and shouldn’t make much of a difference. More
importantly, unless I’m mistaken, it’s rarely going to fire.
> So, somehow when 'maybe-run-git-gc' is called appears to me
> "unpredictable". But anyway. :-)
Sure, but the way I see it, that’s the nature of caches.
> Let move it elsewhere if I am really annoyed.
:-/
Ludo’.