From: "Henzer, Kevin" <KevinHenzer@eaton.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Loss of speedup for subsequent different -but still similar- images build
Date: Thu, 23 Sep 2021 13:02:20 +0000 [thread overview]
Message-ID: <DM6PR17MB3387966C096FE47960185725B5A39@DM6PR17MB3387.namprd17.prod.outlook.com> (raw)
Hello !
Thanks for adding me to the mailing list, and thank for this nice tool that PTXdist is !
I'm new to PTXdist, and I have inherited a build setup that creates two different but quite similar system images, following two different global configurations (config_1 and config_2).
One is the rescue update image of the system, the other the full-featured image. It is using a script to build them both in a row.
Before a recent update, calling the build process successively on those two configurations gave a big speed-up for the second build. The system was reusing most of the packages.
./ptxdist go --ptxconfig=configs/config_1 --platformconfig=configs/platformconfig # takes time only the first time, else quite fast
./ptxdist images --ptxconfig=configs/ config_1 --platformconfig=configs/platformconfig # quite fast
./ptxdist go --ptxconfig=configs/config_2 --platformconfig=configs/platformconfig # quite fast
./ptxdist images --ptxconfig=configs/ config_2 --platformconfig=configs/platformconfig # quite fast
But after updating PTXdist to newer version (now using PTXdist version 2021.03.0), and updating the config files, it seems something has changed, and the outcome is different.
./ptxdist go --ptxconfig=configs/config_1 --platformconfig=configs/platformconfig # takes time at each build
./ptxdist images --ptxconfig=configs/ config_1 --platformconfig=configs/platformconfig # quite fast
./ptxdist go --ptxconfig=configs/config_2 --platformconfig=configs/platformconfig # takes time at each build, seems the system is rebuilding everything
And I got this as first output when switching from one configuration to the other:
-----------------------------------------------------------------
target: host-system-perl.[some hash].cfghash
-----------------------------------------------------------------
Configuration changed! Reconfiguring...
I checked this package and seems to me it is just ensuring that Perl is installed on the host and that the right features are available.
I checked all config options that I think are linked to this package (I searched in rules/host-system-perl.make) :
PTXCONF_HOST_SYSTEM_PERL_BUILD
PTXCONF_HOST_SYSTEM_PERL_JSON
PTXCONF_HOST_SYSTEM_PERL_LOCALE_PO
PTXCONF_HOST_SYSTEM_PERL_XMLPARSER
PTXCONF_HOST_SYSTEM_PERL_YAPP
And they are set the same in both config files.
Still, the hash of this package is changing between each call with different config.
So, I was wondering:
- Can it be that the reconfiguration and "rebuild" of this package is what triggers the full image rebuild?
- If yes, what could trigger this host-system-perl reconfiguration, in your opinion ?
And most important for me, how are those .cfghash computed ? If you have a quick link to the relevant part of the doc, I'll be very happy !
In advance, thanks !
Regards,
Kevin Henzer
-----------------------------
Eaton Industries Manufacturing GmbH ~ Registered place of business: Route de la Longeraie 7, 1110, Morges, Switzerland
-----------------------------
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-09-23 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 13:02 Henzer, Kevin [this message]
2021-09-24 10:23 ` Ian Abbott
2021-09-24 11:33 ` Juergen Borleis
2021-09-29 12:44 ` Michael Olbrich
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=DM6PR17MB3387966C096FE47960185725B5A39@DM6PR17MB3387.namprd17.prod.outlook.com \
--to=kevinhenzer@eaton.com \
--cc=ptxdist@pengutronix.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