Performance Test: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 8: Line 8:
Two identical test systems are used for the results, with all updates available installed. Extra packages installed (besides what's by the default in the distro) are the ones in the Quick Start guide.
Two identical test systems are used for the results, with all updates available installed. Extra packages installed (besides what's by the default in the distro) are the ones in the Quick Start guide.


Romania Setup 1.6 - 2.1
Configuration of the GDC Setup 2.1 - Current master
 
* Ubuntu 12.04 (uname -nr: ubuntu12 3.8.0-31-generic) and
* Fedora 19 (uname -nr: fedora19 3.11.3-201.fc19.x86_64)
 
GDC Setup 2.1 - Current master
 
* Ubuntu 15.10 (Wily Werewolf)" -->  4.2.0-16-generic
* Ubuntu 15.10 (Wily Werewolf)" -->  4.2.0-16-generic
* Fedora release 23 (Twenty Three) --> 4.7.10-100.fc23.x86_64
* Fedora release 23 (Twenty Three) --> 4.7.10-100.fc23.x86_64
* HW configuration: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 16GB RAM,  1 x 600 GB SDD, 1 x 2 TB HDD


All system/distro settings are '''distro's defaults''', that includes:
All system/distro settings are '''distro's defaults''', that includes:
Line 23: Line 18:


- IO scheduler: cfq and CPU governer: ondemand
- IO scheduler: cfq and CPU governer: ondemand
Romania Setup 1.6 - 2.1
*HW config is: SandyBridge i7-2600 CPU @ 3.40GHz (4 cores/8 threads),  8GB RAM,  1 x 500 GB HDD
GDC Setup 2.1 - Current master
*HW config is: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 16GB RAM,  1 x 600 GB SDD, 1 x 2 TB HDD


local.conf it's the default one (the script doesn't touch it except for changing DL_DIR if necessary).
local.conf it's the default one (the script doesn't touch it except for changing DL_DIR if necessary).
Line 36: Line 25:
PARALLEL_MAKE = "-j 8"
PARALLEL_MAKE = "-j 8"
MACHINE = "qemux86"</nowiki>
MACHINE = "qemux86"</nowiki>
In the tables below, unless otherwise noted, sizes are in kilobytes.
Note:
*Master builds are run daily on whatever commit there is when the cron kicks in.
*This page holds a re-run of milestone/RCs builds only for the 1.5 (dora) cycle + 1.4.1/1.4.2 (dylan).
*[https://wiki.yoctoproject.org/wiki/Performance_Test_Weekly_1.5 This page] has the old weekly results ran during the 1.5 cycle. The results differ because the test sytems used there are a bit different than those here (so don't cross compare results).


FAQ:
FAQ:
Line 48: Line 30:
*Q: What's with the different number of RCs? See [[Yocto_Project_Release_Process#Milestone_Releases]]
*Q: What's with the different number of RCs? See [[Yocto_Project_Release_Process#Milestone_Releases]]
*Q: Why are there more results for some commits? The script is ran from a cron job multiple times a day, sometimes master changes daily sometimes it doesn't, hence more results for one commit (ie weekends)
*Q: Why are there more results for some commits? The script is ran from a cron job multiple times a day, sometimes master changes daily sometimes it doesn't, hence more results for one commit (ie weekends)
== Daily Test Results ==
Build performance test suite is run multiple times per day. Latest test reports for master branch can found here:
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf-ubuntu16_master_qemux86.html Ubuntu 16.04]
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf-ubuntu16-xeon_master_qemux86.html Ubuntu 16.04 (Intel® Xeon® HW)]
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf-centos7_master_qemux86.html CentOS 7]
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf-opensuse422_master_qemux86.html OpenSUSE Leap 42.2] (retired)
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf-fedora25_master_qemux86.html Fedora 25] (retired)
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf01_master_qemux86.html Fedora 23] (retired)
* [https://wiki.yoctoproject.org/charts/build_perf/latest/ypperf02_master_qemux86.html Ubuntu 15.10] (retired)


== Milestone Test results ==
== Milestone Test results ==
Line 60: Line 53:
* [https://wiki.yoctoproject.org/charts/perf_milestone/performance_test.html RO Charts]
* [https://wiki.yoctoproject.org/charts/perf_milestone/performance_test.html RO Charts]


Raw test data from the retired Romania test setup has been moved to [[Performance_Test_Old_Results]]
Raw test data from the retired Romania test setup has been moved to
* [[Performance_Test_Old_Results]]
* [[Performance_Test_Weekly_1.5]] has the old weekly results ran during the 1.5 cycle.
 
Configuration for the Romania Setup 1.6 - 2.1:
 
* Ubuntu 12.04 (uname -nr: ubuntu12 3.8.0-31-generic) and
* Fedora 19 (uname -nr: fedora19 3.11.3-201.fc19.x86_64)
* HW configuration: SandyBridge i7-2600 CPU @ 3.40GHz (4 cores/8 threads),  8GB RAM,  1 x 500 GB HDD

Latest revision as of 14:17, 28 January 2019

Build time tracking

Script used for running the builds:

  • Before morty: poky/scripts/contrib/build-perf-test.sh
  • After morty: poky/scripts/oe-build-perf-test

Two identical test systems are used for the results, with all updates available installed. Extra packages installed (besides what's by the default in the distro) are the ones in the Quick Start guide.

Configuration of the GDC Setup 2.1 - Current master

  • Ubuntu 15.10 (Wily Werewolf)" --> 4.2.0-16-generic
  • Fedora release 23 (Twenty Three) --> 4.7.10-100.fc23.x86_64
  • HW configuration: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, 16GB RAM, 1 x 600 GB SDD, 1 x 2 TB HDD

All system/distro settings are distro's defaults, that includes:

- FS mount options: ext4 rw,relatime,data=ordered

- IO scheduler: cfq and CPU governer: ondemand

local.conf it's the default one (the script doesn't touch it except for changing DL_DIR if necessary).

It however exports these in the enviroment: 

BB_NUMBER_THREADS = "8"
PARALLEL_MAKE = "-j 8"
MACHINE = "qemux86"

FAQ:

  • Q: Where is 1.5_M2? It's there but it's called: 1.5_M1.final-412-geaa5df3 The M2 build wasn't released hence no git tag
  • Q: What's with the different number of RCs? See Yocto_Project_Release_Process#Milestone_Releases
  • Q: Why are there more results for some commits? The script is ran from a cron job multiple times a day, sometimes master changes daily sometimes it doesn't, hence more results for one commit (ie weekends)


Daily Test Results

Build performance test suite is run multiple times per day. Latest test reports for master branch can found here:

Milestone Test results

Guadalajara Setup from 2.1 M4 to actual master

Old Test results

Milestone test results from the retired Romania Setup (Yocto 1.6 – 2.1) can be found from here:

Raw test data from the retired Romania test setup has been moved to

Configuration for the Romania Setup 1.6 - 2.1:

  • Ubuntu 12.04 (uname -nr: ubuntu12 3.8.0-31-generic) and
  • Fedora 19 (uname -nr: fedora19 3.11.3-201.fc19.x86_64)
  • HW configuration: SandyBridge i7-2600 CPU @ 3.40GHz (4 cores/8 threads), 8GB RAM, 1 x 500 GB HDD
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Performance_Test&oldid=46678"