GNU bug report logs - #71357
[PATCH] substitute: Don’t keep cache entries more than a few days.

Previous Next

Package: guix-patches;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Tue, 4 Jun 2024 08:08:02 UTC

Severity: normal

Tags: patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 71357 <at> debbugs.gnu.org, Josselin Poiret <dev <at> jpoiret.xyz>, Simon Tournier <zimon.toutoune <at> gmail.com>, Mathieu Othacehe <othacehe <at> gnu.org>, Tobias Geerinckx-Rice <me <at> tobias.gr>, Ricardo Wurmus <rekado <at> elephly.net>, Andreas Enge <andreas <at> enge.fr>, Christopher Baines <guix <at> cbaines.net>
Subject: [bug#71357] [PATCH] substitute: Don’t keep cache entries more than a few days.
Date: Thu, 13 Jun 2024 11:50:29 +0200
Hi,

Christopher Baines <mail <at> cbaines.net> skribis:

> This sounds good to me.

Thanks, pushed as 7e00fb9f31f51ac2f9fa67b71a3eb8aaa23efdb6.  I’ll update
the ‘guix’ package soonish.

> I think one of the problems on bayfront is that each substitute process
> looks and decides it's time to remove the expired cache entries. For
> every new process that starts and decides to join it, it probably slows
> them all down. This is very similar to a "thundering herd" since the
> processes trip over each other trying to delete the same files.

Oh right.  I’m not sure if this is what I was seeing, but it can
definitely be a problem on build machines.  We should change (guix
cache) to avoid that.

Thanks!

Ludo’.




This bug report was last modified 1 year and 32 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.