From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: poky <poky@pokylinux.org>
Subject: Re: Further build profiling info
Date: Wed, 16 Feb 2011 20:49:02 +0000 [thread overview]
Message-ID: <1297889342.11289.302.camel@rex> (raw)
In-Reply-To: <1297807550.11289.171.camel@rex>
On Tue, 2011-02-15 at 22:05 +0000, Richard Purdie wrote:
> I'm sending these notes to the list since they might be useful to others
> and it archives them.
>
> Timing a build with license.bbclass:
> consisting of 4847 tasks:
>
> real 107m23.857s
> user 376m31.640s
> sys 46m51.020s
>
> Without license.bbclass:
> 4409 tasks:
>
> real 107m46.881s
> user 369m6.670s
> sys 46m19.890s
>
> Without the setscene task and without license.bbclass:
>
> 3970 tasks:
>
> real 105m36.940s
> user 364m6.900s
> sys 45m33.950s
>
> which makes sense as setscene is a critical path dependency whilst the
> license checks are not.
We've had some fixes into master which:
* improve the pseudo-native build time (worth 2 minutes)
* shorten the rpm rootfs creation times
* enabling parallel builds for some packages
* Improve the task processing/creation latency (worth 1-2 minutes)
The time for the same build as above is now taking:
real 97m1.204s
user 385m24.460s
sys 48m30.990s
(4848 tasks)
and this is despite adding in some extra documentation generation pieces
too (which accounts for the extra user time) so quite a nice
improvement. Nice work but I think there is further low hanging fruit to
gain a little more time back too! :)
Cheers,
Richard
next prev parent reply other threads:[~2011-02-16 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:05 Further build profiling info Richard Purdie
2011-02-16 20:49 ` Richard Purdie [this message]
2011-02-24 15:40 ` Richard Purdie
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=1297889342.11289.302.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@pokylinux.org \
/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