From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/1] sstate: do not keep intermediate sstate files
Date: Thu, 24 Feb 2022 08:36:28 +0100 [thread overview]
Message-ID: <20220224073629.23717-1-ubely@ilbers.de> (raw)
Sstate is quite demanding for disk space. And it often causes failures
in CI, related to 'out-of-space'.
This patchset minimizes space usage by intermediate state files by
removing them:
- after sstate-cache populated: with separate task in task queue
- after sstate-cache unpacked: by direct call of this task
Some results shown below for three different cases:
- sstate disabled;
- sstate enabled;
- sstate enabled + cleanup patch.
bullseye-arm64 cross build with full IMAGE_INSTALL list:
$ sudo du -sh build-*
5,7G build-nosstate
12G build-sstate
7,6G build-sstate-cleanup
bullseye-arm64 cross build with empty IMAGE_INSTALL list:
$ sudo du -sh build-*
2,5G build-nosstate
5,3G build-sstate
3,4G build-sstate-cleanup
bullseye-amd64 native build with empty IMAGE_INSTALL list:
$ sudo du -sh build-*
3,2G build-nosstate
6,4G build-sstate
4,2G build-sstate-cleanup
Changes since v1:
- patchset renamed from "sstate: compress rootfs sstate files";
- sstate intermediate files compression replaced by removing;
- dpkg intermediate files are also handled.
Uladzimir Bely (1):
sstate: do not keep intermediate sstate files
meta/classes/dpkg-base.bbclass | 7 +++++++
meta/classes/rootfs.bbclass | 7 +++++++
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 7 +++++++
3 files changed, 21 insertions(+)
--
2.20.1
next reply other threads:[~2022-02-24 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 7:36 Uladzimir Bely [this message]
2022-02-24 7:36 ` [PATCH v2 1/1] " Uladzimir Bely
2022-02-24 7:56 ` [PATCH v2 0/1] " Schmidt, Adriaan
2022-02-24 8:19 ` Uladzimir Bely
2022-02-24 9:04 ` Schmidt, Adriaan
2022-02-24 15:57 ` Henning Schild
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=20220224073629.23717-1-ubely@ilbers.de \
--to=ubely@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