Performance Test
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.
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)
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
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
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).
It however exports these in the enviroment:
BB_NUMBER_THREADS = "8" PARALLEL_MAKE = "-j 8" MACHINE = "qemux86"
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).
- 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:
- 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)
Milestone Test results
The results are split in tow different phases as below
Romania Setup from 1.6 to 2.1 releases
Guadalajara Setup from 2.1 M4 to actual master
