From: Stefan Stanacar <stefanx.stanacar@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] script to run build tests and collect time metrics
Date: Fri, 29 Mar 2013 17:10:19 +0200 [thread overview]
Message-ID: <cover.1364568244.git.stefanx.stanacar@intel.com> (raw)
Hello,
This script runs a series of standard tests and collects some metrics
(wall clock and size of tmp/). It takes care of dropping vm caches
(for which it need sudo access) and doing a fetchall first.
It uses /usr/bin/time to measure the wall clock for builds (not bash
internal time command).
The metrics collected are:
* time bitbake core-image-sato and size of tmp/ dir without sstate
* time bitbake virtual/kernel
* time bitbake core-image-sato and size of tmp/ without sstate but with rm_work enabled
* time bitbake core-image-sato -c rootfs with sstate
* three parsing time metrics (bitbake -p) with and without tmp/cache.
The results are collected in build-perf-test/globalres.log for all commits
that it has run, and in a separate folder for ech run (called results-<rev>-<date>)
This is the same script used to collect the results for:
https://wiki.yoctoproject.org/wiki/Performance_Test#1.4_Perfomance_Data
It's still a work in progress and needs some improvements but it should be a good starting point.
Regards,
Stefan
The following changes since commit 2f4fe1ee111a3dff68ac1cea6f3f6767cd6fe4eb:
bitbake: hob: Search strings and results should be persistent (2013-03-29 10:41:25 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib stefans/perf-test
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stefans/perf-test
Stefan Stanacar (4):
scripts/contrib/build-perf-test.sh: add a script for build performance
tracking
scripts/contrib/build-perf-test.sh: add a global results file
scripts/contrib/build-perf-test.sh: add option to allow cherry-picking
of fix revisions
scripts/contrib/build-perf-test.sh: add timings for bitbake -p
scripts/contrib/build-perf-test.sh | 348 +++++++++++++++++++++++++++++++++++++
1 file changed, 348 insertions(+)
create mode 100755 scripts/contrib/build-perf-test.sh
--
1.8.1.4
next reply other threads:[~2013-03-29 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 15:10 Stefan Stanacar [this message]
2013-03-29 15:10 ` [PATCH 1/4] scripts/contrib/build-perf-test.sh: add a script for build performance tracking Stefan Stanacar
2013-03-29 15:10 ` [PATCH 2/4] scripts/contrib/build-perf-test.sh: add a global results file Stefan Stanacar
2013-03-29 15:10 ` [PATCH 3/4] scripts/contrib/build-perf-test.sh: add option to allow cherry-picking of fix revisions Stefan Stanacar
2013-03-29 15:10 ` [PATCH 4/4] scripts/contrib/build-perf-test.sh: add timings for bitbake -p Stefan Stanacar
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=cover.1364568244.git.stefanx.stanacar@intel.com \
--to=stefanx.stanacar@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.