From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Set XZ_COMPRESSION_LEVEL to -9
Date: Sat, 13 Apr 2019 09:52:56 +0300 [thread overview]
Message-ID: <20190413065256.GB10988@localhost> (raw)
In-Reply-To: <CAMKF1srHOayZ_MVHrwEA=54XD7HS5D5jT_fYmqF84mYuJ-cjEw@mail.gmail.com>
On Fri, Apr 12, 2019 at 04:12:19PM -0700, Khem Raj wrote:
> On Fri, Apr 12, 2019 at 2:09 PM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > It is consistent with other compressors also using their
> > best compression.
> >
> > xz is currently the option that offers best compression,
> > using settings even lower than the default is surprising
> > and makes it harder to choose the best available compression.
> >
> > For anyone who cares about compression time using a different
> > option like gzip or bzip2 is the logical choice.
> >
> > For decompression, better compressed is actually faster
> > to decompress.
>
> I worry about resources we need to spend when creating these archives.
> Can you post some comparisons
> along to assess the performance.
On my laptop single-threaded compression of an image I am frequently
building takes 20s with -3 and 55s with -9.
Building the whole image from scratch takes more than 2 hours.
If you care about resources spent, I remember it saved me around 10
minutes build time when I changed OPKGBUILDCMD from the default "xz -6"
to "gzip -1" - for the common case where package feeds are not used
there is no point in spending time on compression and decompression.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-04-13 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 21:09 [PATCH] Set XZ_COMPRESSION_LEVEL to -9 Adrian Bunk
2019-04-12 21:44 ` Andre McCurdy
2019-04-13 6:17 ` Adrian Bunk
2019-04-12 23:12 ` Khem Raj
2019-04-13 6:52 ` Adrian Bunk [this message]
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=20190413065256.GB10988@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.