All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ian Ray" <ian.ray@ge.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: EXT: Re: [OE-core] [PATCH V2] archiver: Configurable tarball compression
Date: Wed, 22 Sep 2021 11:29:41 +0300	[thread overview]
Message-ID: <20210922082941.GA47151@zoo6.em.health.ge.com> (raw)
In-Reply-To: <a06209fe-c772-7a28-bde8-4627fef58296@bootlin.com>

On Tue, Sep 21, 2021 at 03:48:29PM +0200, Michael Opdenacker wrote:
> 
> On 9/21/21 3:20 PM, Michael Opdenacker wrote:
> > By the way, zstd seems to be marginally worse (+1%) than xz in terms of
> > compressed size, but is orders of magnitude faster (see
> > https://archlinux.org/news/now-using-zstandard-instead-of-xz-for-package-compression/).
> 
> 
> Actually, this article only mentions decompression speed, but that's
> also true for compression speed.
> 
> Here are my own tests:
> 
> mike@mike-laptop:~/tmp$ time gzip linux-5.15-rc2.tar
> 
> real    0m29.293s
> user    0m28.712s
> sys    0m0.553s
> 
> mike@mike-laptop:~/tmp$ time xz linux-5.15-rc2.tar
> 
> real    7m2.658s
> user    7m1.096s
> sys    0m1.280s
> 
> mike@mike-laptop:~/tmp$ time zstd linux-5.15-rc2.tar
> linux-5.15-rc2.tar   : 16.29%   (1136803840 => 185233271 bytes,
> linux-5.15-rc2.tar.zst)
> 
> real    0m5.476s
> user    0m5.530s
> sys    0m0.864s
> 
> mike@mike-laptop:~/tmp$ ls -la linux-5.15*
> -rw-rw-r-- 1 mike mike 1136803840 Sep 21 15:31 linux-5.15-rc2.tar
> -rw-rw-r-- 1 mike mike  198135832 Sep 21 15:24 linux-5.15-rc2.tar.gz
> -rw-rw-r-- 1 mike mike  125980548 Sep 21 15:26 linux-5.15-rc2.tar.xz
> -rw-rw-r-- 1 mike mike  185233271 Sep 21 15:31 linux-5.15-rc2.tar.zst
> 
> So, here the claim that zstd (with default options) is almost as good as
> xz in compressed size is not confirmed. However, zstd is a clear winner
> in terms of compression speed, and anyway better than gzip. This is
> worth switching.

Thank you for measuring this!  

I will re-submit the patch when we update to a more recent Yocto
version.


> 
> Cheers
> 
> Michael
> 
> -- 
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
> 
> 


  reply	other threads:[~2021-09-22  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  6:15 [PATCH V2] archiver: Configurable tarball compression Ian Ray
2021-09-21 12:18 ` [OE-core] " Richard Purdie
2021-09-21 13:20   ` Michael Opdenacker
     [not found]   ` <16A6D8EA388563F3.1316@lists.openembedded.org>
2021-09-21 13:48     ` Michael Opdenacker
2021-09-22  8:29       ` Ian Ray [this message]
2021-10-27 11:31       ` Martyn Welch

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=20210922082941.GA47151@zoo6.em.health.ge.com \
    --to=ian.ray@ge.com \
    --cc=michael.opdenacker@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.