From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v5 4/7] isar-bootstrap: Use tar output instead of directory
Date: Wed, 18 Oct 2023 16:52:29 +0300 [thread overview]
Message-ID: <6ed09972-c4b3-4db4-ae12-951f0b6087ba@ilbers.de> (raw)
In-Reply-To: <20231018085125.378989-5-amikan@ilbers.de>
Hello,
Just some statistics to proof zst compression choosing.
Building mc:qemuarm64-bookworm:isar-image-base with 3 types of bootstrap tar
compression gives the following measurements:
| bootstrap, sec | chroot1, sec | chroot2, sec
gz | 73 | 80 | 88
xz | 76 | 82 | 89
zst | 68 | 80 | 88
where:
bootstrap - do_bootstrap task of isar-bootstrap-target
chroot1 - do_rootfs_install task of sbuild-chroot-target
chroot2 - do_rootfs_install task of sbuild-chroot-target-db2m
(chroot1 and chroot2 are performing in parallel)
next prev parent reply other threads:[~2023-10-18 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 8:51 [PATCH v5 0/7] Migrate to mmdebstrap Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 1/7] meta: Switch " Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 2/7] meta: Preinstall apt for Ubuntu and RPi targets Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 3/7] isar-bootstrap: Move preparations to hooks Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 4/7] isar-bootstrap: Use tar output instead of directory Anton Mikanovich
2023-10-18 13:52 ` Anton Mikanovich [this message]
2023-10-18 8:51 ` [PATCH v5 5/7] user_manual.md: Replace debootstrap with mmdebstrap Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 6/7] user_manual.md: Update minimal host requirements Anton Mikanovich
2023-10-18 8:51 ` [PATCH v5 7/7] isar-bootstrap: Remove unused code Anton Mikanovich
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=6ed09972-c4b3-4db4-ae12-951f0b6087ba@ilbers.de \
--to=amikan@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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