From: Baurzhan Ismagulov <ibr@radix50.net>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: Better way to handle apt cache needed
Date: Wed, 28 Dec 2022 10:21:56 +0100 [thread overview]
Message-ID: <Y6wKtPgPRoR+1FNX@ilbers.de> (raw)
In-Reply-To: <371e4d826cca6aaba11a4222fef547b134ed6ce7.camel@siemens.com>
On Wed, Dec 28, 2022 at 09:02:13AM +0000, Moessbauer, Felix wrote:
> The root cause for that behavior is the apt cache
> (deb_dl_dir_(import|export)), that copies all previously downloaded apt
> packages into the WORKDIR of each (bitbake) package.
> Given, that a common apt-cache is around 2GB and 8 tasks are run in
> parallel, this gives already 16GB for the tasks, and 7 * 2GB for the
> buildchroots (host and target), in total ~30GB.
Thanks Felix for the report. IIRC, it was previously mounted and was supposed
to be converted to per-package hardlinks to parallelize sbuild instances and
ease debugging (by knowing later which exact snapshot was fed to a specific
build). We use small (1- / 2-TB) SSDs as job storage and a huge increase would
have been noticeable... We'll check.
With kind regards,
Baurzhan
next prev parent reply other threads:[~2022-12-28 9:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 9:02 Moessbauer, Felix
2022-12-28 9:21 ` Baurzhan Ismagulov [this message]
2022-12-28 9:45 ` Moessbauer, Felix
2022-12-28 10:23 ` Uladzimir Bely
2022-12-28 11:04 ` Moessbauer, Felix
2022-12-29 23:15 ` Roberto A. Foglietta
2022-12-30 4:38 ` Uladzimir Bely
2022-12-30 7:08 ` Roberto A. Foglietta
2022-12-30 6:05 ` Moessbauer, Felix
2022-12-30 8:27 ` Roberto A. Foglietta
2022-12-30 10:04 ` Moessbauer, Felix
2022-12-30 13:11 ` Moessbauer, Felix
2022-12-30 13:33 ` Roberto A. Foglietta
2022-12-30 13:47 ` Roberto A. Foglietta
2022-12-31 8:59 ` Roberto A. Foglietta
2022-12-31 21:03 ` Roberto A. Foglietta
2023-01-09 8:12 ` Roberto A. Foglietta
2023-01-09 9:58 ` Roberto A. Foglietta
2023-01-19 18:08 ` Roberto A. Foglietta
2023-01-25 4:48 ` Roberto A. Foglietta
2023-02-10 16:05 ` Roberto A. Foglietta
2023-02-14 10:01 ` Roberto A. Foglietta
2023-02-14 16:46 ` Roberto A. Foglietta
2022-12-30 12:29 ` Roberto A. Foglietta
2022-12-28 9:22 ` Florian Bezdeka
2023-01-02 16:15 ` Henning Schild
2023-01-05 6:31 ` Uladzimir Bely
2023-01-05 17:10 ` 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=Y6wKtPgPRoR+1FNX@ilbers.de \
--to=ibr@radix50.net \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@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