unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Efraim Flashner <efraim@flashner.co.il>,
	Akib Azmain Turja <akib@disroot.org>,
	guix-devel@gnu.org
Subject: Re: First guix pull is too costly
Date: Fri, 01 Jul 2022 17:25:46 +0200	[thread overview]
Message-ID: <878rpconwl.fsf@gmail.com> (raw)
In-Reply-To: <87k08x3sjv.fsf@gnu.org>

Hi,

On ven., 01 juil. 2022 at 14:51, Ludovic Courtès <ludo@gnu.org> wrote:

> I was thinking we could have a “Git checkout cache daemon”, so that
> things currently in ~/.cache/guix/checkouts could somehow be shared
> safely among users.

Yeah, maybe Git worktree could be used.  Aide the optimization of the
first “guix pull”, the current design is not totally safe when “guix
time-machine” is intensively run:

        The issue is because concurrency.  If two time-machines are run
        concurrently, they both update ~/.cache/guix/checkouts/ and the
        end result is hard to predict.

        <https://yhetil.org/guix/86r18k1ylf.fsf@gmail.com>


> (That doesn’t help with the first ‘guix pull’ though.)

Yeah, but can we do better than mirroring Savannah and maintain a list
of supported mirrors?


Cheers,
simon


  reply	other threads:[~2022-07-01 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  8:04 First guix pull is too costly Akib Azmain Turja
2022-06-28 10:05 ` bokr
2022-06-28 11:23 ` zimoun
2022-06-28 12:28   ` Efraim Flashner
2022-06-28 16:59     ` zimoun
2022-07-01 12:51       ` Ludovic Courtès
2022-07-01 15:25         ` zimoun [this message]
2022-06-28 12:49   ` Akib Azmain Turja
2022-06-28 17:09     ` zimoun
2022-06-28 17:40       ` Akib Azmain Turja
2022-07-01 12:52   ` Ludovic Courtès
2022-07-07  9:01     ` Giovanni Biscuolo

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rpconwl.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=akib@disroot.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).