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: Wed, 25 Jan 2023 05:48:36 +0100 [thread overview]
Message-ID: <CAJGKYO6WTGR_boeWnrU31TDwgqx1oTzgRqk5vmPC=qLEzQ3S+A@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO7A-mH=3a3cibj9tS3fKnecpmNEe0vuH1CO3z7xN0o3Dw@mail.gmail.com>
On Thu, 19 Jan 2023 at 19:08, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> Hi all,
>
> Thanks to Uladzimir who pointed me out about the weirdness of ln -P in sbuild
> and other changes that I made, nvpriv7 is clearly faster than npriv6. Here
> below the benchmarks compared with the original based on robang74:next.
>
> Thanks to Uladzimir who pointed me out about the weirdness of ln -P in sbuild
> and other changes that I made, nvpriv7 is clearly faster than npriv6. Here
> below the benchmarks compared with the original based on robang74:next.
>
> devel2 (public) + npriv7 (private)
> ------------------------------------
> fresh cache
> ------------ basic-os --------------
> 3745 Mb (max) | 3182 Mb (max)
> 2849 Mb (rest) | 2289 Mb (rest)
> 3596 Mb (deb) | 3596 Mb (deb)
> 806 Mb (wic) | 806 Mb (wic)
> 551 Mb (cache) | 551 Mb (cache)
> time: 2m39s | time: 30s 5.30x
This 2m39s is wrong: it refers to a reduced image that I created for
test and I committed some hours ago
https://github.com/robang74/isar-nvidia-debian/commit/7ea25b486484b2f675bc1a94098dd22fb08594f0
The real number is 3m6s for the current npriv.8 - while 30s has been
reduced at 28s. Sorry for the mistake, my fault.
> ------------ original ---------------------
> time: 7m58s | time: 2m17s 3.48x
> 3.00x | 4.57x
> |
> ------------ complete --------------
> 33197 Mb (max) | 28209 Mb (max)
> 23964 Mb (rest) | 18982 Mb (rest)
> 3596 Mb (deb) | 3596 Mb (deb)
> 9143 Mb (wic) | 9139 Mb (wic)
> 4916 Mb (cache) | 4916 Mb (cache)
> time: 12m45s | time: 4m11s 3.05x
> ------------ original ---------------------
> time: 21m17s | time: 8m28s 2.51x
> 1.67x | 2.02x
>
> About the complete image, we need to consider some fixed times like these:
>
> * time to produce complete wic image: 2m23s
> * time to compile nvidia drivers: 2m8s
>
> Because these times cannot be shrink as part of the building process then we can
> subtract that times (for the cache just producing the image because the drivers
> are cached) and revise the benchmarks as following:
>
> fresh cache
> ------------ complete --------------
> time: 8m14s | time: 1m48s 4.57x
> ------------ original ---------------------
> time: 16m46s | time: 6m05s 2.76x
> 2.03x | 3.38x
>
> Even in the worst case, the building performances has been increased by 2x
>
> Best regards, R-
--
Roberto A. Foglietta
+49.176.274.75.661
+39.349.33.30.697
next prev parent reply other threads:[~2023-01-25 4:49 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
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 [this message]
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='CAJGKYO6WTGR_boeWnrU31TDwgqx1oTzgRqk5vmPC=qLEzQ3S+A@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