From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: guix-devel@gnu.org
Subject: Re: Are gzip-compressed substitutes still used?
Date: Wed, 17 Mar 2021 19:20:07 +0100 [thread overview]
Message-ID: <2368135b-5f20-1e9a-3ff2-e0bff8ed5a02@web.de> (raw)
In-Reply-To: <87im5p3dsq.fsf@gnu.org>
On 17.03.21 18:12, Ludovic Courtès wrote:
> (See
> <https://lists.gnu.org/archive/html/guix-devel/2021-01/msg00378.html>
> for the initial message.)
>
> Here’s an update, 1.5 month later. This time I’m looking at nginx logs
> covering Feb 8th to Mar 17th and using a laxer regexp than in the
> message above, here are the gzip/lzip download ratio for several
> packages:
>
> --8<---------------cut here---------------start------------->8---
> ludo@berlin ~$ ./nar-download-stats.sh /tmp/sample3.log gtk%2B-3: gzip/lzip ratio: 37/3255 1%
> glib-2: gzip/lzip ratio: 97/8629 1%
> coreutils-8: gzip/lzip ratio: 81/2306 3%
> python-3: gzip/lzip ratio: 120/7177 1%
> r-minimal-[34]: gzip/lzip ratio: 8/302 2%
> openmpi-4: gzip/lzip ratio: 19/236 8%
> hwloc-2: gzip/lzip ratio: 10/43 23%
> gfortran-7: gzip/lzip ratio: 6/225 2%
> --8<---------------cut here---------------end--------------->8---
Interesting findings...
> Conclusion? It still sounds like we can’t reasonably remove gzip
> support just yet.
>
> I’d still like to start providing zstd-compressed substitutes though.
> So I think what we can do is:
>
> • start providing zstd substitutes on berlin right now so that when
> 1.2.1 comes out, at least some substitutes are available as zstd;
>
> • when 1.2.1 is announced, announce that gzip substitutes may be
> removed in the future and invite users to upgrade;
My personal substitution servers runs with lzip + zstd, so no gzip. It
works fine, but I didn't had any "legacy" users. Although zstd is only
0,6% of lzip in regards to total downloads over the last months...
next prev parent reply other threads:[~2021-03-17 18:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:20 When substitute download + decompression is CPU-bound Ludovic Courtès
2020-12-14 22:29 ` Julien Lepiller
2020-12-14 22:59 ` Nicolò Balzarotti
2020-12-15 7:52 ` Pierre Neidhardt
2020-12-15 9:45 ` Nicolò Balzarotti
2020-12-15 9:54 ` Pierre Neidhardt
2020-12-15 10:03 ` Nicolò Balzarotti
2020-12-15 10:13 ` Pierre Neidhardt
2020-12-15 10:14 ` Pierre Neidhardt
2020-12-15 11:42 ` Ludovic Courtès
2020-12-15 12:31 ` Pierre Neidhardt
2020-12-18 14:59 ` Ludovic Courtès
2020-12-18 15:33 ` Pierre Neidhardt
2020-12-15 11:36 ` Ludovic Courtès
2020-12-15 11:45 ` Nicolò Balzarotti
2020-12-15 10:40 ` Jonathan Brielmaier
2020-12-15 19:43 ` Joshua Branson
2021-01-07 10:45 ` Guillaume Le Vaillant
2021-01-07 11:00 ` Pierre Neidhardt
2021-01-07 11:33 ` Guillaume Le Vaillant
2021-01-14 21:51 ` Ludovic Courtès
2021-01-14 22:08 ` Nicolò Balzarotti
2021-01-28 17:53 ` Are gzip-compressed substitutes still used? Ludovic Courtès
2021-03-17 17:12 ` Ludovic Courtès
2021-03-17 17:33 ` Léo Le Bouter
2021-03-17 18:08 ` Vagrant Cascadian
2021-03-18 0:03 ` zimoun
2021-03-18 16:00 ` Vagrant Cascadian
2021-03-18 18:53 ` Leo Famulari
2021-03-20 11:23 ` Ludovic Courtès
2021-03-17 18:06 ` zimoun
2021-03-17 18:20 ` Jonathan Brielmaier [this message]
2021-03-18 17:25 ` Pierre Neidhardt
2021-01-15 8:10 ` When substitute download + decompression is CPU-bound Pierre Neidhardt
2021-01-28 17:58 ` Ludovic Courtès
2021-01-29 9:45 ` Pierre Neidhardt
2021-01-29 11:23 ` Guillaume Le Vaillant
2021-01-29 11:55 ` Nicolò Balzarotti
2021-01-29 12:13 ` Pierre Neidhardt
2021-01-29 13:06 ` Guillaume Le Vaillant
2021-01-29 14:55 ` Nicolò Balzarotti
2021-02-01 22:18 ` Ludovic Courtès
2021-01-29 13:33 ` zimoun
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=2368135b-5f20-1e9a-3ff2-e0bff8ed5a02@web.de \
--to=jonathan.brielmaier@web.de \
--cc=guix-devel@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).