From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: What's the state of (guix build download-nar)?
Date: Tue, 11 Apr 2023 15:34:31 +0200 [thread overview]
Message-ID: <87edoqk0ew.fsf@gmail.com> (raw)
In-Reply-To: <87a61mhqkp.fsf@gmail.com>
Hi,
On jeu., 09 févr. 2023 at 09:16, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Currently it’s used by some of the (guix VCS-download) modules. I think
>> we should just update to (1) use lzip instead of gzip, and (2) have it
>> check ci.guix.gnu.org + bordeaux.guix.gnu.org.
>
> How about using zstd? I'm proposing it instead of lzip, because long
> term, I think we want to reduce the size of our storage requirements and
> offer a single compression type for our NARs, which zstd would be ideal
> (it's faster and compresses close enough to lzip).
I guess it’s the same direction as this thread [1],
When substitute download + decompression is CPU-bound
Ludovic Courtès <ludo@gnu.org>
Mon, 14 Dec 2020 23:20:17 +0100
id:87im94qbby.fsf@gnu.org
especially this Guillaume’s message [2] comparing various methods. The
possible agenda [3] concluding the thread was, quoting:
We could do that. I suppose a possible agenda would be:
1. Start providing zstd susbstitutes anytime. However, most clients
will keep choosing lzip because it usually compresses better.
2. After the next release, stop providing lzip substitutes and provide
only gzip + zstd-19.
This option has the advantage that it wouldn’t break any installation.
It’s not as nice as the ability to choose a download strategy, as we
discussed earlier, but implementing that download strategy sounds
tricky.
Well, to be honest, I am a bit lost about the compression methods;
especially when also considering this old blog post [4].
As the subject of this thread is asking: “What's the state of (guix
build download-nar)?” ;-)
1: https://yhetil.org/guix/87im94qbby.fsf@gnu.org/#r
2: https://yhetil.org/guix/87ft3d2fge.fsf@yamatai
3: https://yhetil.org/guix/87bld9j651.fsf@gnu.org
4: https://guix.gnu.org/en/blog/2019/substitutes-are-now-available-as-lzip/
Cheers,
simon
prev parent reply other threads:[~2023-04-11 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:25 What's the state of (guix build download-nar)? Christopher Baines
2023-02-08 9:08 ` Ludovic Courtès
2023-02-08 9:24 ` Christopher Baines
2023-03-11 20:42 ` Christopher Baines
2023-02-09 14:16 ` Maxim Cournoyer
2023-02-09 15:41 ` Christopher Baines
2023-04-11 13:34 ` Simon Tournier [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
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=87edoqk0ew.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@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.
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).