From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Cc: Josh Lock <joshua.lock@intel.com>, Tom Rini <tom_rini@mentor.com>
Subject: build performance: bb-matrix on 4-core (BB_NUMBER_THREADS and PARALLEL_MAKE optimization)
Date: Wed, 06 Jul 2011 11:16:38 -0700 [thread overview]
Message-ID: <4E14A686.5020104@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
I ran the attached bb-matrix.sh on the following system:
CPU (1): Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
Cores: 4
Threads: 8
Memory: 8186560 kB
OS Disk: INTEL SSDSA2M040G2GC (SSD)
Build Disk: Hitachi HDT721050SLA360 (Spinning Media)
The script runs builds with all combinations of BB_NUMBER_THREADS and
PARALLEL_MAKE from 4 through 16.
Once BB_NUMBER_THREADS hit 10, the kernel OOM Killer started killing off
tasks and build time tripled. Those runs have been removed the dataset.
All of the runs with PARALLEL_MAKE=10 also failed, for a variety of
reasons. See bb-pm-errors.txt for details. For whatever reason, 10 seems
to be a bad number. Additional failures were seen at 09-11 and 10-14.
These have all been removed from the dat file.
From the remaining results, a clear downward trend in build time is
evident with increasing BB_NUMBER_THREADS through 8, while build time
mostly increases again with 9 (and dramatically so with 10, not shown).
Optimal build time is achieved with BB_NUMBER_THREADS=8.
Along the BB_NUMBER_THREADS=8 line, there is no clear trend with
increasing values of PARALLEL_MAKE. Local downward trends appear from
4-7 and from 11-14. Optimal build time occurs with PARALLEL_MAKE=14,
however, it only bests PARALLEL_MAKE=7 by 68 seconds.
While optimal build time is achieved with BB=8 and PM=14, a more
resource friendly setting of BB=8 and PM=6 yields nearly as good results.
To reproduce the plots and get an interactive view that you can rotate:
$ gnuplot --persist < bb-pm-matrix.plt
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
[-- Attachment #2: bb-pm-runtime-fear-jul6.dat --]
[-- Type: application/ms-tnef, Size: 6460 bytes --]
[-- Attachment #3: plot.png --]
[-- Type: image/png, Size: 14106 bytes --]
[-- Attachment #4: plot-bb.png --]
[-- Type: image/png, Size: 8406 bytes --]
[-- Attachment #5: plot-pm.png --]
[-- Type: image/png, Size: 9011 bytes --]
[-- Attachment #6: bb-matrix.sh --]
[-- Type: application/x-shellscript, Size: 1558 bytes --]
[-- Attachment #7: bb-pm-matrix.plt --]
[-- Type: text/plain, Size: 385 bytes --]
set xlabel "BB_NUMBER_THREADS"
set ylabel "PARALLEL_MAKE"
set zlabel "Build Time (seconds)"
set dgrid3d 13,6
set pm3d at b
set ticslevel 0.8
set term png
set output "plot.png"
splot "bb-pm-runtime-fear-jul6.dat" u 1:2:3 with lines
set view 90,0
set output "plot-bb.png"
replot
set view 90,90
set output "plot-pm.png"
replot
set view 60,30
set term wxt
replot
next reply other threads:[~2011-07-06 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 18:16 Darren Hart [this message]
2011-07-07 10:39 ` build performance: bb-matrix on 4-core (BB_NUMBER_THREADS and PARALLEL_MAKE optimization) Richard Purdie
2011-07-07 18:12 ` Darren Hart
2011-07-08 20:44 ` Robert Berger
2011-07-09 8:36 ` Darren Hart
2011-07-09 21:16 ` Chris Larson
2011-07-10 7:13 ` Darren Hart
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=4E14A686.5020104@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=joshua.lock@intel.com \
--cc=poky@yoctoproject.org \
--cc=tom_rini@mentor.com \
/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.