From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Nicolò Balzarotti" <anothersms@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: When substitute download + decompression is CPU-bound
Date: Tue, 15 Dec 2020 11:13:43 +0100 [thread overview]
Message-ID: <87a6ufbcmg.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87k0tjo085.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Nicolò Balzarotti <anothersms@gmail.com> writes:
> If you download multiple files at a time, you might end up decompressing
> them simultaneously. Plzip won't help then on a dual core machine,
> where you might end up being cpu bound again then. Is this right?
>
> If it is, reducing the overall cpu usage seems to be a better approach
> in the long term.
An answer to this may be in pipelining the process.
The parallel downloads would feed the archives to the pipeline and the
parallel decompressor would pop the archives out of the pipeline one by
one.
If I'm not mistaken, this should yield optimal results regardless of the
network or CPU performance.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-12-15 10:14 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 [this message]
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
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=87a6ufbcmg.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=anothersms@gmail.com \
--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).