Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Performance measurement: Building openembedded-core with and without overclocking on C-i7 2600K
Date: Tue, 18 Oct 2011 15:40:59 +0200	[thread overview]
Message-ID: <4E9D81EB.50702@telia.com> (raw)
In-Reply-To: <20111018121936.GA23902@ad.chargestorm.se>

2011-10-18 14:19, Anders Darander skrev:
> * Ulf Samuelsson<ulf_samuelsson@telia.com>  [111018 14:06]:
>> 2011-10-18 08:28, Anders Darander skrev:
>>> * Ulf Samuelsson<ulf_samuelsson@telia.com>   [111017 22:45]:
>>>> If anyone is interested...
>>> Build stats are always interesting... ;)
>>>> Same machine in two different configurations.
>>>> .........................................................#1...........................#2
>>>> P8Z68V Pro
>>>> Core-i7 2600K @                             3.4 GHz..................4.4 GHz
>>>> 8 GB @ ...........................................1333
>>>> MHz...............1640 MHz
>>>> 1TB WD Black 7200 RPM
>>>> Ubuntu 11-10
>>>> Almost all source code already in source directory
>>> This would severely restrict the usefulness of the comparison. I'd guess
>>> that this means that in one case the source will be downloaded, while
>>> it'll already be downloaded in the second test. Could you redo the
>>> statistics with all sources downloaded?
>> I had already built it once before running the first test then updated
>> and I think one additional package was downloaded over a 100 MBps line
>> so it affects a little, but not too much.
> Ok, just curious. Not least as you had one image fail in the first
> configuration, which you attributed to a failed download. That remark
> made me wonder...

OK, To be 100% correct:
I built meta-toolchain first so all packages for that build should be there.
This is much longer than anything else, so this is a good comparision.

Then the build #1 was started and measruements was taken.
This failed for core-image-sato due to one missing package, which
After build #1 was completed, I downloaded the missing package
and started build #2.

>
> Cheers,
> Anders
>
>> I think the conclusion:
>>       Increasing the CPU speed by 30% and the memory frequency by 20%
>>       gives 10-15% faster build time is OK.
>>>> Building meta-toolchain is 13% faster with overclocking.
>>> Was the overclocking test run after the non-overclocking?
>


-- 
Best Regards
Ulf Samuelsson




      reply	other threads:[~2011-10-18 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 20:44 Performance measurement: Building openembedded-core with and without overclocking on C-i7 2600K Ulf Samuelsson
2011-10-17 22:13 ` Khem Raj
2011-10-18  6:03   ` Ulf Samuelsson
2011-10-18 14:44     ` Khem Raj
2011-10-18 14:47     ` Phil Blundell
2011-10-18 22:34       ` Ulf Samuelsson
2011-10-23 17:50     ` Roman Khimov
2011-10-23 21:50       ` Ulf Samuelsson
2011-10-29 14:23       ` Raffaele Recalcati
2011-10-18  6:28 ` Anders Darander
2011-10-18 12:05   ` Ulf Samuelsson
2011-10-18 12:19     ` Anders Darander
2011-10-18 13:40       ` Ulf Samuelsson [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=4E9D81EB.50702@telia.com \
    --to=ulf_samuelsson@telia.com \
    --cc=openembedded-devel@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