From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Performance datapoint - impact of static libs
Date: Fri, 15 Jul 2011 14:31:02 +0100 [thread overview]
Message-ID: <1310736662.20015.1232.camel@rex> (raw)
Before:
real 104m1.135s
user 415m57.560s
sys 61m31.180s
With "--disable-static" being passed to configure (changes below):
real 99m46.645s
user 383m32.390s
sys 60m42.170s
So static libs add an extra ~30mins of processing (7%) and ~5 mins to
the overall build time. Not as much of a gain as I'd have liked but
interesting none the less.
The changes were effectively:
DISABLESTATIC = "--disable-static"
DISABLESTATIC_pn-sqlite3-native = ""
DISABLESTATIC_pn-openssl = ""
DISABLESTATIC_pn-openssl-native = ""
DISABLESTATIC_pn-qemu-native = ""
EXTRA_OECONF_append = " ${DISABLESTATIC}"
in local.conf with a patch to the openjade-native recipe to not install
the .a file using oe_libinstall and a patch to apmd to fix a libtool
related compiling bug in its makefile.
Cheers,
Richard
next reply other threads:[~2011-07-15 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 13:31 Richard Purdie [this message]
2011-07-15 13:37 ` Performance datapoint - impact of static libs Phil Blundell
2011-07-20 14:50 ` 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=1310736662.20015.1232.camel@rex \
--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