From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] core/instrumentation: shave minutes off the build time
Date: Mon, 19 Mar 2018 21:04:58 +0100 [thread overview]
Message-ID: <87o9jjltlh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180319175010.0c26763b@windsurf> (Thomas Petazzoni's message of "Mon, 19 Mar 2018 17:50:10 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Mon, 19 Mar 2018 16:30:52 +0000, Trent Piepho wrote:
>> After fixing s/L/l/, here are the timings for a 15 minute build:
>>
>> configure 510.29
>> build 166.12
>> extract 45.53
>> other 43.88
>> hostinstall 35.43
>> check_host_rpath 33.37
>> check_bin_arch 28.30
>> targetinstall 23.37
>> stageinstall 15.97
>> step_pkg_size 9.49
> Thanks for those measurements. I still find it a bit annoying that we
> spend 1m10sec on instrumentation related topics on a 15 minutes build.
> The use of ccache makes the build time lower than it normally is, and
> therefore makes the instrumentation cost even more visible, but using
> ccache is a valid use case.
Agreed, Buildroot has always been about low overhead and fast builds.
> Should we move the check_host_rpath and check_bin_arch checks as
> finalize hooks, instead of running them at the end of each package
> installation ? We can always get the package that installed the "bogus"
> file through the package-file-list*.txt files, no ?
I would think so as well. Anybody interested in giving it a shot?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-19 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 20:35 [Buildroot] [PATCH 0/2] core/instrumentation: optimisations Yann E. MORIN
2018-03-15 20:35 ` [Buildroot] [PATCH 1/2] core/intrumetnation: don't spawn to get seconds-since-EPOCH Yann E. MORIN
2018-03-17 11:54 ` Cam Hutchison
2018-03-18 16:16 ` Yann E. MORIN
2018-03-19 16:15 ` Trent Piepho
2018-03-15 20:35 ` [Buildroot] [PATCH 2/2] core/instrumentation: shave minutes off the build time Yann E. MORIN
2018-03-18 14:14 ` Peter Korsgaard
2018-03-18 16:15 ` Yann E. MORIN
2018-03-18 16:33 ` Peter Korsgaard
2018-03-22 16:41 ` Thomas De Schampheleire
2018-03-22 16:50 ` Thomas Petazzoni
2018-03-22 17:11 ` Thomas De Schampheleire
2018-03-22 17:25 ` Trent Piepho
2018-03-22 22:39 ` Peter Korsgaard
2018-03-23 22:39 ` Arnout Vandecappelle
2018-03-23 23:03 ` Thomas Petazzoni
2018-03-19 16:30 ` Trent Piepho
2018-03-19 16:50 ` Thomas Petazzoni
2018-03-19 20:04 ` Peter Korsgaard [this message]
2018-03-20 21:47 ` Trent Piepho
2018-03-19 16:53 ` Peter Korsgaard
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=87o9jjltlh.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.