public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v2 0/1] sstate: do not keep intermediate sstate files
Date: Thu, 24 Feb 2022 07:56:48 +0000	[thread overview]
Message-ID: <AS4PR10MB531869DB55E7F77CD13DEE09ED3D9@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220224073629.23717-1-ubely@ilbers.de>

Uladzimir Bely, 24. Februar 2022 08:36:
> Sstate is quite demanding for disk space. And it often causes failures
> in CI, related to 'out-of-space'.

If those few GB cause problems, then you really need a larger disk :)
But I get the point, and I agree that we should try to save space.

> This patchset minimizes space usage by intermediate state files by
> removing them:
> - after sstate-cache populated: with separate task in task queue

I would like to avoid adding extra tasks. There seems to be a hook
to insert functions (SSTATEPOSTCREATEFUNCS), but as sstate is not
really documented, I have not yet figured out how to make our use case work.

> - 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.

It's unnecessary for dpkg, because we use hardlinks to the *.deb file,
so no extra disk space is consumed for the sstate preparation.

Adriaan

> 
> 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
> 
> --
> You received this message because you are subscribed to the Google Groups
> "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/20220224073629.23717-1-
> ubely%40ilbers.de.

  parent reply	other threads:[~2022-02-24  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  7:36 Uladzimir Bely
2022-02-24  7:36 ` [PATCH v2 1/1] " Uladzimir Bely
2022-02-24  7:56 ` Schmidt, Adriaan [this message]
2022-02-24  8:19   ` [PATCH v2 0/1] " 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=AS4PR10MB531869DB55E7F77CD13DEE09ED3D9@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
    --to=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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