From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package-infra: limit the number of // jobs
Date: Sat, 11 May 2013 22:51:46 +0200 [thread overview]
Message-ID: <87vc6pz1ct.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1368194161-27851-1-git-send-email-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Fri, 10 May 2013 15:56:01 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Yann> The current code spawns as many jobs as up to twice the number of
Yann> CPUs.
Yann> On small-class machines like laptops, with a limitted amount of
Yann> memory, but still a few CPUs (real or hyperthreads), the HDD
Yann> becomes a bottleneck, and it becomes almost impossible to do
Yann> anythiong else while there is a build in progress.
Yann> Limit the number of jobs to the number of CPUs plus one.
Yann> Even on fast machines with fast HDDs, this settings keeps the
Yann> machine fully busy (for those packages that can build in
Yann> parallel, of course).
Yann> For example, building qemu or the linux kernel kept my
Yann> hyperthreaded hexa Core i7 with 18GiB of RAM, busy at 99% (I
Yann> never ever managed to get 100% even with more jobs, not even
Yann> 200); while on my hyperthreaded dual Core i5 with only 4GiB and a
Yann> slow HDD, I still topped at 100% CPU, while still able to do some
Yann> work involving the HDD.
Yes, I remember the old default being pretty hard on my old laptop with
spinning rust. With a SSD I don't really notice it much.
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-05-11 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 13:56 [Buildroot] [PATCH v2] package-infra: limit the number of // jobs Yann E. MORIN
2013-05-10 14:07 ` Thomas Petazzoni
2013-05-10 14:12 ` Nathan Lynch
2013-05-11 20:51 ` Peter Korsgaard [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=87vc6pz1ct.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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