From: Guillaume Le Vaillant <glv@posteo.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: When substitute download + decompression is CPU-bound
Date: Thu, 07 Jan 2021 12:33:10 +0100 [thread overview]
Message-ID: <87czyh2d8p.fsf@yamatai> (raw)
In-Reply-To: <87czyhc8q2.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Wow, impressive! :)
>
> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Note that the plots only show the results using only 1 thread and
>
> Doesn't 1 thread defeat the purpose of parallel compression / decompression?
>
It was just to get a better idea of the relative compression and
decompression speeds of the algorithms. When using n threads, if the
file is big enough, the speeds are almost multiplied by n and the
compression ratio is a little lower.
>> Machine used for the tests:
>> - CPU: Intel i7-3630QM
>> - RAM: 16 MiB
>
> I suppose you meant 16 GiB ;)
Yes, of course :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-07 11:33 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 [this message]
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=87czyh2d8p.fsf@yamatai \
--to=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).