From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/7] automatically set PARALLEL_JOBS when BR2_JLEVEL is 0
Date: Thu, 14 Jun 2012 10:33:35 +0200 [thread overview]
Message-ID: <20120614083335.GA15879@mail.sceen.net> (raw)
In-Reply-To: <4FD921C9.4020302@mind.be>
On Thu, Jun 14, 2012 at 01:27:05AM +0200, Arnout Vandecappelle wrote:
> In my experience, you need 2 times the number of CPUs to fully utilize
> the processor because most compilations have long iowait latencies.
Unless you have little memory, this is no longer true, and as some
compilations can eat a lot of memory, doubling their number reduces the
amount of available page cache, potentially increasing the amount of
I/O. Using the number of available processors should be just fine.
--
Richard Braun
next prev parent reply other threads:[~2012-06-14 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:09 [Buildroot] [PATCH 0/7] automatically determine job concurrency Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 1/7] introduce PARALLEL_JOBS build system variable Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 2/7] boost: change uses of BR2_JLEVEL to PARALLEL_JOBS Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 3/7] cmake: change use " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 4/7] midori: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 5/7] qt: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 6/7] toolchain/crosstool-ng: " Nathan Lynch
2012-06-12 2:09 ` [Buildroot] [PATCH 7/7] automatically set PARALLEL_JOBS when BR2_JLEVEL is 0 Nathan Lynch
2012-06-13 23:27 ` Arnout Vandecappelle
2012-06-13 23:44 ` Nathan Lynch
2012-06-14 6:07 ` Peter Korsgaard
2012-06-14 6:16 ` Nathan Lynch
2012-06-14 8:56 ` Peter Korsgaard
2012-06-14 8:33 ` Richard Braun [this message]
2012-06-14 15:02 ` [Buildroot] [PATCHv2 " Nathan Lynch
2012-06-14 18:09 ` Baruch Siach
2012-06-16 19:37 ` [Buildroot] [PATCHv3 " Nathan Lynch
2012-06-24 9:13 ` [Buildroot] [PATCH 0/7] automatically determine job concurrency Peter Korsgaard
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=20120614083335.GA15879@mail.sceen.net \
--to=rbraun@sceen.net \
--cc=buildroot@busybox.net \
/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