Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: poky <poky@pokylinux.org>
Subject: Further build profiling info
Date: Tue, 15 Feb 2011 22:05:50 +0000	[thread overview]
Message-ID: <1297807550.11289.171.camel@rex> (raw)

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.

So a 120 second reduction for a drop of 439 tasks so a 0.27 second
overhead per task assuming they were all critical path. Numbers from the
graph suggested a 0.5 second task overhead so perhaps 50% were critical
path.

Interesting numbers and it suggests the situation isn't as bad as the
graph makes out though.

Cheers,

Richard




             reply	other threads:[~2011-02-15 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 22:05 Richard Purdie [this message]
2011-02-16 20:49 ` Further build profiling info Richard Purdie
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=1297807550.11289.171.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