[oe] Performance measurement: Building openembedded-core with and without overclocking on C-i7 2600K

[Ulf Samuelsson]

2011-10-18 14:19, Anders Darander skrev:
> * Ulf Samuelsson<ulf_samuelsson at telia.com>  [111018 14:06]:
>> 2011-10-18 08:28, Anders Darander skrev:
>>> * Ulf Samuelsson<ulf_samuelsson at 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