[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: When substitute download + decompression is CPU-bound
From: |
Pierre Neidhardt |
Subject: |
Re: When substitute download + decompression is CPU-bound |
Date: |
Tue, 15 Dec 2020 11:13:43 +0100 |
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/
signature.asc
Description: PGP signature
- When substitute download + decompression is CPU-bound, Ludovic Courtès, 2020/12/14
- Re: When substitute download + decompression is CPU-bound, Ludovic Courtès, 2020/12/15
- Re: When substitute download + decompression is CPU-bound, Pierre Neidhardt, 2020/12/15
- Re: When substitute download + decompression is CPU-bound, Ludovic Courtès, 2020/12/18
- Re: When substitute download + decompression is CPU-bound, Pierre Neidhardt, 2020/12/18
Re: When substitute download + decompression is CPU-bound, Ludovic Courtès, 2020/12/15
Re: When substitute download + decompression is CPU-bound, Jonathan Brielmaier, 2020/12/15