From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Performance regression (binutils and gold)
Date: Sun, 12 Apr 2015 14:49:12 +0200 [thread overview]
Message-ID: <20150412124912.GA2328@jama> (raw)
In-Reply-To: <1428828331.6976.14.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Sun, Apr 12, 2015 at 09:45:31AM +0100, Richard Purdie wrote:
> To allow us to upgrade to the latest binutils we ended up enabling
> building of gold. Unfortunately this is clearly visible on our
> performance benchmarks, it leads to a 3-4 minute speed loss in overall
> build time :(.
>
> Locally, benchmarks for building binutils-cross show:
>
> Just ld:
>
> 95.87user 48.36system 1:05.66elapsed 219%CPU (0avgtext+0avgdata
> 162480maxresident)k
> 0inputs+1030184outputs (0major+7753895minor)pagefaults 0swaps
>
> with gold:
>
> 366.22user 67.25system 1:14.29elapsed 583%CPU (0avgtext+0avgdata
> 435488maxresident)k
> 248inputs+1205792outputs (1major+12572236minor)pagefaults 0swaps
> richard@dax:/media/build1/poky/build2$
>
> So whilst it only takes 10 seconds longer overall for me on what is a
> pretty powerful machine, you can see a huge increase in user time and
> CPU usage. I believe that on our slower quad core performance benchmark
> machine, this equates to a few minutes.
>
> The question is therefore, do we have a better way to fix things? Is
> this performance drop acceptable?
It's acceptable for me, I think most people with slower machines (with
less ram) are already using ls-is-gold, so it won't make any difference
for them.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2015-04-12 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 8:45 Performance regression (binutils and gold) Richard Purdie
2015-04-12 9:15 ` Khem Raj
2015-04-12 12:49 ` Martin Jansa [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=20150412124912.GA2328@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.