From: Ross Burton <ross.burton@intel.com>
To: "Bjørn Forsman" <bjorn.forsman@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: for a quad-core machine, shouldn't parallelism be set to 8?
Date: Wed, 9 Jan 2013 19:35:24 +0000 [thread overview]
Message-ID: <89ACB277BC7047D58E19B3BA98CE24F0@intel.com> (raw)
In-Reply-To: <CAEYzJUHQ8c4NDErbcjNyRLKg3NfENUrFo6JO1xdL71dZsXyzrA@mail.gmail.com>
On Wednesday, 9 January 2013 at 18:42, Bjørn Forsman wrote:
> > # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
> > # be appropriate for example.
> >
> > i thought the general rule was that parallelism should be *twice*
> > the number of cores. that's certainly what's suggested in the yocto
> > QS guide:
>
>
>
> Some time ago I wrote a script to build the linux kernel 3 times at
> each -jN level from 1 to 50. Then I averaged the build time on each
> -jN level. I got the fastest build with -jNCPUS. Going above NCPUS
> just added overhead, although very little. The overhead seemed to
> build up quite linearly from above -jNCPUS. Because the overhead is so
> little, having -jNCPUS*2 may not be noticeably slower than -jNCPUS.
>
> I ran the same benchmark another machine and it showed the same trend
> curve. Note that NCPUS must include the hyperthread cores.
Of course if you set BB_NUM_THREADS and PARALLEL_MAKE to NCPUS, then you're actually potentially running NCPUS*NCPUS compile threads. I'm not convinced that NCPUS*2 is useful with that considered.
Ross
prev parent reply other threads:[~2013-01-09 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 12:55 for a quad-core machine, shouldn't parallelism be set to 8? Robert P. J. Day
2013-01-09 14:20 ` Elvis Dowson
2013-01-09 14:26 ` Robert P. J. Day
2013-01-09 14:34 ` Martin Jansa
2013-01-09 17:55 ` Scott Garman
2013-01-09 18:42 ` Bjørn Forsman
2013-01-09 19:35 ` Ross Burton [this message]
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=89ACB277BC7047D58E19B3BA98CE24F0@intel.com \
--to=ross.burton@intel.com \
--cc=bjorn.forsman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox