From: Adrian Bunk <bunk@stusta.de>
To: Stefan Agner <stefan@agner.ch>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 2/2] image_types: add Zstandard conversion support
Date: Wed, 20 Nov 2019 12:31:45 +0200 [thread overview]
Message-ID: <20191120103145.GA23054@localhost> (raw)
In-Reply-To: <20191120091258.30350-2-stefan@agner.ch>
On Wed, Nov 20, 2019 at 09:12:58AM +0000, Stefan Agner wrote:
>...
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -59,6 +59,8 @@ XZ_INTEGRITY_CHECK ?= "crc32"
>
> ZIP_COMPRESSION_LEVEL ?= "-9"
>
> +ZSTD_COMPRESSION_LEVEL ?= "-3"
> +
>...
Why -3 and not -19 ?
Compression speed is not a real issue, and AFAIR decompression
tends to be slightly faster with smaller compressed size.
Plus the benefit that smaller images are faster to load
from network/storage.
cu
Adrian
next prev parent reply other threads:[~2019-11-20 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 9:12 [PATCH v4 1/2] zstd: move recipe to oe-core from meta-oe Stefan Agner
2019-11-20 9:12 ` [PATCH v4 2/2] image_types: add Zstandard conversion support Stefan Agner
2019-11-20 10:31 ` Adrian Bunk [this message]
2019-11-20 10:48 ` Alex Kiernan
2019-11-20 10:49 ` Alex Kiernan
2019-11-20 12:27 ` Stefan Agner
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=20191120103145.GA23054@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan@agner.ch \
/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