From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "ubely@ilbers.de" <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/5] Improving apt cache
Date: Sat, 21 Jan 2023 05:12:13 +0100 [thread overview]
Message-ID: <CAJGKYO6dZAGS8zZVJ=q7kqjparrOChb=Q12t_Fp8n_B=EU2ozg@mail.gmail.com> (raw)
In-Reply-To: <8de12074d8eac2fd540fda3a576d0ae344b27628.camel@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
On Fri, 20 Jan 2023 at 14:04, Moessbauer, Felix <
felix.moessbauer@siemens.com> wrote:
> On Fri, 2023-01-20 at 08:31 +0100, Uladzimir Bely wrote:
> > Currently, apt cache (e.g. `var/cache/apt/archives`) import and
> > export
> > functions are not optimal. Multiple files are copied from global
> > DL_DIR to package WORKDIR, increasing disk IO and space 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 ans sstate caches.
>
> I tested this series (v3) in two layers: amd64 (internal) and arm64
> (meta-iot2050) and can confirm that it works. Also we get a significant
> performance improvement and massively reduced disk consumption.
>
>
The candidate describes the following situation in plain straight words:
Q: input: ln -sf, output: cp -Ln
A: much ado for nothing (cit.)
Q: How does the candidate execute the tests on the system?
A: I don't but my gut feelings
Q: What alternative does the candidate propose?
A: an elegant solution because quality is relative but elegance is absolute
(cit.)
Q: summarise it in a nerd language
A:
mkdir tmp && ( cd tmp; mkdir a b
echo pippo > a/file.txt
ln -sf $PWD/a/file.txt b
cat a/file.txt b/file.txt
# pippo
# pippo
echo pluto >b/file.txt
cat a/file.txt b/file.txt
# pluto
# pluto
rm -f b/file.txt
echo ciao >b/file.txt
cat a/file.txt b/file.txt
# pluto
# ciao
cp -Ln b/file.txt a/file
cat a/file.txt b/file.txt
# pluto
# ciao
cd ..; rm -rf tmp ) # to repeat in loop
Enjoy, R-
[-- Attachment #2: Type: text/html, Size: 2379 bytes --]
next prev parent reply other threads:[~2023-01-21 4:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 7:31 Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 1/5] Clean apt cache from debootstrapped rootfs dirs Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 2/5] Use hardlinks in deb-dl-dir import/export Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 3/5] Exclude apt cache from sstate caches Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 4/5] Use symlinks when importing debian packages to sbuild chroot Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 5/5] Lightweight copy of rootfs directories if possible Uladzimir Bely
2023-01-20 13:04 ` [PATCH v3 0/5] Improving apt cache Moessbauer, Felix
2023-01-21 4:12 ` Roberto A. Foglietta [this message]
2023-01-24 7:38 ` Uladzimir Bely
2023-01-30 8:45 ` Moessbauer, Felix
2023-01-30 9:56 ` Roberto A. Foglietta
2023-01-30 10:04 ` Roberto A. Foglietta
2023-01-30 10:45 ` Henning Schild
2023-01-30 12:24 ` Roberto A. Foglietta
2023-01-30 14:16 ` 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='CAJGKYO6dZAGS8zZVJ=q7kqjparrOChb=Q12t_Fp8n_B=EU2ozg@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=felix.moessbauer@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