public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: henning.schild@siemens.com,
	Adriaan Schmidt <adriaan.schmidt@siemens.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2] use xz and gzip on host (outside chroot)
Date: Tue, 16 Aug 2022 18:11:18 +0300	[thread overview]
Message-ID: <cf7c541c-9ad5-a295-f2c5-ce3684ae9e91@ilbers.de> (raw)
In-Reply-To: <20220808073613.133842-1-felix.moessbauer@siemens.com>

08.08.2022 10:36, Felix Moessbauer wrote:
> From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
>
> This patch significantly speeds up the final image compression
> as the compression itself is no longer emulated.
>
> For gzip, no additional dep has to be installed on the system,
> for xz the xz-utils package has to be installed but this will
> be required from bitbake 2.0 on anyways.
>
> Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
> Acked-by: Felix Moessbauer <felix.moessbauer@siemens.com>

Hello,

I've made some investigations to collect compression speed statistics on
qemuarm64-bullseye Isar target with 490Mb rootfs. Here are the results:

XZ:
Buildchroot xz (QEMU):   45.305s
Host xz:                 18.783s

GZIP:
Buildchroot gzip (QEMU):   4m30.155s
Host gzip:                 1m30.135s
Buildchroot gzip (native): 1m27.162s

Buildchroot pigz (QEMU):     32.265s
Host pigz:                   13.131s

So it looks reasonable to use native compression and we really need to think
about removing ISAR_CROSS_COMPILE="0" for imager.
We also can try to use parallelized pigz for gzip compression.


  parent reply	other threads:[~2022-08-16 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  7:36 Felix Moessbauer
2022-08-08 15:30 ` Henning Schild
2022-08-15 10:47   ` Baurzhan Ismagulov
2022-08-16 15:11 ` Anton Mikanovich [this message]
2022-08-30 15:38   ` Moessbauer, Felix

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=cf7c541c-9ad5-a295-f2c5-ce3684ae9e91@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.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