public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH 0/6] imagetypes
Date: Tue, 8 Mar 2022 13:50:44 +0000	[thread overview]
Message-ID: <AM9PR10MB486958AA64B948421DC8190C89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220210062446.4145565-1-adriaan.schmidt@siemens.com>

Hi Adriaan,

> -----Original Message-----
> From: isar-users@googlegroups.com <isar-users@googlegroups.com> On
> Behalf Of Adriaan Schmidt
> Sent: Thursday, February 10, 2022 7:25 AM
> To: isar-users@googlegroups.com
> Cc: Schmidt, Adriaan (T CED SES-DE) <adriaan.schmidt@siemens.com>
> Subject: [PATCH 0/6] imagetypes
> 
> This series introduces image types and conversions as known from OE.
> The main motivation is to provide a more flexible way of generating and
> processing images, without the need to insert custom tasks (e.g., currently
> we have custom classes adding tasks for things like bz2 or xz compression of
> images in several downstream layers).
> 
> These patches have been tested on some of our layers, and also work with
> some more "challenging" use cases like image-in-image recipes and custom
> image types brought by layers.
> 
> It's not perfect (e.g., documentation is still missing). Also I added just the
> bare minimum of conversions, so there should probably be follow-ups for
> additional compressions, or things like checksums, which can also be nicely
> done with this.

While testing this on larger images, I observed that the compression times for "wic.xz" are much higher than with the manual approach in our internal recipes.
This is due to the XZ_OPTIONS = "-T0 -M200" and default compression level. Compared to XZ_OPTIONS = "-T0 -9" (less compression, no memory limit), the patch version is almost a magnitude slower (20 min vs 3min).
Maybe we should just provide better default options here.

Best regards,
Felix

  parent reply	other threads:[~2022-03-08 13:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  6:24 Adriaan Schmidt
2022-02-10  6:24 ` [PATCH 1/6] image: remove IMAGE_SUFFIX Adriaan Schmidt
2022-02-10  6:24 ` [PATCH 2/6] image: refactor SDK Adriaan Schmidt
2022-02-10  6:24 ` [PATCH 3/6] meta: introduce IMAGE_CMD_* Adriaan Schmidt
2022-02-18 14:55   ` Anton Mikanovich
2022-02-10  6:24 ` [PATCH 4/6] imagetypes: restructure files Adriaan Schmidt
2022-02-10  6:24 ` [PATCH 5/6] imagetypes: switch meta-isar to the new scheme Adriaan Schmidt
2022-02-18 14:56   ` Anton Mikanovich
2022-02-10  6:24 ` [PATCH 6/6] meta-isar: remove IMAGE_FSTYPES from multiconfig definitions Adriaan Schmidt
2022-03-03 18:35 ` [PATCH 0/6] imagetypes Anton Mikanovich
2022-03-03 18:55   ` Henning Schild
2022-03-03 19:04     ` Schmidt, Adriaan
2022-03-03 20:46       ` Henning Schild
2022-03-04 17:54     ` Anton Mikanovich
2022-03-07  6:41       ` Jan Kiszka
2022-03-08 13:50 ` Moessbauer, Felix [this message]
2022-03-31  5:56   ` Schmidt, Adriaan
2022-03-08 14:10 ` Moessbauer, Felix
2022-03-31  5:57   ` Schmidt, Adriaan

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=AM9PR10MB486958AA64B948421DC8190C89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --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