All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Josh Lock <joshua.lock@intel.com>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>,
	Tom Rini <tom_rini@mentor.com>
Subject: Re: build performance: bb-matrix on 4-core (BB_NUMBER_THREADS and PARALLEL_MAKE optimization)
Date: Thu, 07 Jul 2011 11:39:33 +0100	[thread overview]
Message-ID: <1310035173.20015.820.camel@rex> (raw)
In-Reply-To: <4E14A686.5020104@linux.intel.com>

On Wed, 2011-07-06 at 11:16 -0700, Darren Hart wrote:
> 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.

Thanks Darren, I think those are interesting results.

Is the general advice we should give out therefore to set
BB_NUMBER_THREADS = PARALLEL_MAKE = number threads?

I'd love to understand why there is the peak and second dip on the
PARALLEL_MAKE curve...

It would also be good to put the script in scripts/contrib.

Cheers,

Richard



  reply	other threads:[~2011-07-07 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 18:16 build performance: bb-matrix on 4-core (BB_NUMBER_THREADS and PARALLEL_MAKE optimization) Darren Hart
2011-07-07 10:39 ` Richard Purdie [this message]
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=1310035173.20015.820.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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.