public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
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>,
	 "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"ibr@radix50.net" <ibr@radix50.net>,
	 "Schild, Henning" <henning.schild@siemens.com>
Subject: Re: Better way to handle apt cache needed
Date: Sat, 31 Dec 2022 09:59:26 +0100	[thread overview]
Message-ID: <CAJGKYO4MWCs_7gdMOAXeAF91S6P1UkoPpeNPcTbaoOgLtUCEAA@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO6PjGa8p2Cf+kqrtPMG3FCLP=+LnxFddjctKtBnmJak5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 738 bytes --]

Hi all,

 sorry for the image but some numbers should be displayed in a proper
form. I continued to work on the building optimization of ISAR and the
results are quite interesting. Almost 2x with some great achievements
in some specific areas like cache reduction (22x) or in some
particular cases like using a little of the repository downloaded
which brings to a disk usage reduced by 11x times. About building
time, the ratios are a little under-estimated because network
downloads for debootstrap and apt update take a fixed time that cannot
be reduced. My first tests indicate that also custom debian packages
and repackaged .deb are correctly deployed into the system despite the
changes. More tests are welcome.

 Best regards, R-

[-- Attachment #2: isar-building-performance-gains.png --]
[-- Type: image/png, Size: 40824 bytes --]

  reply	other threads:[~2022-12-31  9:00 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
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 [this message]
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=CAJGKYO4MWCs_7gdMOAXeAF91S6P1UkoPpeNPcTbaoOgLtUCEAA@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=ibr@radix50.net \
    --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