From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Improving apt cache
Date: Fri, 30 Dec 2022 05:38:56 +0100 [thread overview]
Message-ID: <20221230043858.15411-1-ubely@ilbers.de> (raw)
Currently, apt cache (e.g. `var/cache/apt/archives`) import and export
functions are not optimal. Multiple files are imported from global
DL_DIR to package WORKDIR, increasing disk IO and size needed.
Also, various chroots (bootstrap, buildchroot, sbuild chroot) include
their apt caches to sstate cache files.
This patchset switches to hardlinks instead of copies and removes apt
cache from bootstrapped images.
Currently (measured on qemuarm64-bullseye cross-compilation with
maximum 8 parallel tasks (e.g. 8 CPU cores)):
- build directory size reduced from 8878 to 7594 MiB
- runtime maximum disk usage reduced from 16018 to 12479 MiB
TODO:
- cleanup other rootfs's (sbuild-chroot, buildchroot)
- deal with additional copying in sbuild routines
Uladzimir Bely (2):
Use hardlinks in deb-dl-dir functions
Clean apt cache from debootstrapped rootfs dirs
meta/classes/deb-dl-dir.bbclass | 4 ++--
meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 6 ++++++
2 files changed, 8 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2022-12-30 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 4:38 Uladzimir Bely [this message]
2022-12-30 4:38 ` [PATCH 1/2] Use hardlinks in deb-dl-dir functions Uladzimir Bely
2022-12-30 7:29 ` Moessbauer, Felix
2022-12-30 8:29 ` Roberto A. Foglietta
2022-12-30 4:38 ` [PATCH 2/2] Clean apt cache from debootstrapped rootfs dirs Uladzimir Bely
2022-12-30 9:03 ` Roberto A. Foglietta
2023-01-02 16:27 ` Henning Schild
2023-01-02 16:33 ` Henning Schild
2023-01-03 9:01 ` Roberto A. Foglietta
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=20221230043858.15411-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