From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Some further build dependency timings
Date: Fri, 14 Oct 2011 12:34:53 +0100 [thread overview]
Message-ID: <1318592102.942.1.camel@ted> (raw)
In-Reply-To: <1318430990.23801.176.camel@ted>
On Wed, 2011-10-12 at 15:49 +0100, Richard Purdie wrote:
> On Wed, 2011-10-12 at 09:40 -0500, Mark Hatle wrote:
> > It would be interesting to determine first off, if there is anywhere pseudo
> > should be running that it currently isn't. And second if this is simply due to
> > LD_PRELOAD time, or if enabling the jump table is the culprit.
> >
> > One potential optimization, when PSEUDO_DISABLE=1 is to only setup the jump
> > table entries for fork/exec items.
>
> Agreed, I don't know where the time is being spent exactly at this
> point. I do know we execute an absolute ton of exec/fork calls so
> removing any overhead from them will improve our speed though. This
> change means do_configure won't run with pseudo enabled for example
> which is a very exec heavy task.
So we did some tests, I thought I'd share the results:
base build config:
real 38m12.356s
user 236m4.710s
sys 39m38.180s
adding in the psuedo patches but not enabling (effectively jitter
measurement):
real 38m13.034s
user 235m44.250s
sys 39m6.150s
enabling the lazy linking:
real 38m16.121s
user 236m1.300s
sys 39m45.860s
Enable PSEUDO_UNLOAD:
real 35m46.281s
user 233m56.750s
sys 37m51.400s
So the big win isn't the linking, its the unloading of pseudo when we
don't need it...
Cheers,
Richard
prev parent reply other threads:[~2011-10-14 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 20:45 Some further build dependency timings Richard Purdie
2011-10-11 11:35 ` Richard Purdie
2011-10-12 14:40 ` Mark Hatle
2011-10-12 14:49 ` Richard Purdie
2011-10-14 11:34 ` Richard Purdie [this message]
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=1318592102.942.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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