From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Michael Adler <michael.adler@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] feat: add zstd support to image conversions
Date: Tue, 24 Jan 2023 13:05:37 +0100 [thread overview]
Message-ID: <CAJGKYO63oukR=wB7k+Vhs_MJWn+y_yxrv4xB1Gr2O0CkCzcv9g@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO5qxEdBEWFsRLq-1KuE8+2VRbBNYfCfdKLdBa=PL-YDow@mail.gmail.com>
On Tue, 24 Jan 2023 at 04:17, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> Il Lun 23 Gen 2023, 20:22 Jan Kiszka <jan.kiszka@siemens.com> ha scritto:
>>
>> On 23.01.23 15:00, Michael Adler wrote:
>> > This patch enables ISAR to build zstd compressed images.
>> >
>>
>> I was briefly thinking you had solved the dpkg vs. zstd issue - just a
>> dream :)
>
>
> Hi Jan.
>
> I think you are speaking about zstd compression for the debian package that is 1% bigger but 13x times faster in expanding. [1]
[...]
>
> The alternative is to repackage everything with xz parallel. Usually a modern laptop has 8 pipes but I have the sensation that with -T 0 it counts just the cores because on my machine spawn 4 not 8.
Forget about the last 4 instead of 8 about xz. Every compressor is
doing the same on my laptop and it is a complete novelty. Possibly the
newer versions spawn with limitation to not clog the machine.
Yes, all 8 CPUs (4 cores X 2 threads) are online and account for every
command that gives access to them (lscpu, proc, nproc, htop, etc.).
Something similar on your machines?
Best regards, R-
next prev parent reply other threads:[~2023-01-24 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 14:00 Michael Adler
2023-01-23 19:22 ` Jan Kiszka
2023-01-24 3:17 ` Roberto A. Foglietta
2023-01-24 12:05 ` Roberto A. Foglietta [this message]
2023-02-09 11:35 ` Uladzimir Bely
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJGKYO63oukR=wB7k+Vhs_MJWn+y_yxrv4xB1Gr2O0CkCzcv9g@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=michael.adler@siemens.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox