From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Performance numbers
Date: Mon, 06 Feb 2012 13:01:15 +0000 [thread overview]
Message-ID: <1328533275.24049.16.camel@ted> (raw)
Its been a while since we had some performance numbers and there were
recently some questions about how current build time compared to
previous numbers.
On my 12 core system, build time for qemux86 from scratch is ~42
minutes. This compares favourably with previous numbers from that
system. Interestingly, switching to qemumips resulted in a build time of
43 minutes in the same tmpdir suggesting that the native part of the
bootstrap process isn't the bottleneck.
On the quad core (the system used for many of the previous numbers I'd
provided), build time for qemux86 was 105 minutes which again is roughly
consistent with where things were for 1.1.
So things haven't changed much recently which is as I'd expect. We
haven't seen many performance related patches but its good to know
things aren't regressing either.
Cheers,
Richard
next reply other threads:[~2012-02-06 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 13:01 Richard Purdie [this message]
2012-02-06 13:28 ` Performance numbers Eric Bénard
2012-02-06 13:32 ` Martin Jansa
2012-02-06 13:57 ` Richard Purdie
2012-02-06 15:28 ` Khem Raj
2012-02-06 16:22 ` 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=1328533275.24049.16.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