From: Rebecca Cran <rebecca@bluestop.org>
To: "Brian J. Johnson" <brian.johnson@hpe.com>,
"Wei, David" <david.wei@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Lu, ShifeiX A" <shifeix.a.lu@intel.com>,
"Zimmer, Vincent" <vincent.zimmer@intel.com>,
Andrew Fish <afish@apple.com>
Subject: Re: Improvements to build system etc. for edk2-platforms devel-MinnowBoard3?
Date: Thu, 23 Feb 2017 12:10:03 -0700 [thread overview]
Message-ID: <e2e07aef-aefa-32da-87bc-60237bf7efa2@bluestop.org> (raw)
In-Reply-To: <c359b576-3c9f-c024-9b0e-86a192b46d23@hpe.com>
On 2/23/2017 11:53 AM, Brian J. Johnson wrote:
> Sorry if I'm bikeshedding... NUMBER_OF_PROCESSORS isn't a good
> default for those of us who build on servers with hundreds of threads
> available. The OS, disks, and build.exe/build.py become bottlenecks.
> Maybe we could put a cap (say, 20) on the default thread limit, so it
> uses NUMBER_OF_PROCESSORS or 20 threads, whichever is less.
>
> Or just set a small, fixed number of threads by default and document
> better how to change it, as others suggested.
Good point. I think the best approach will be to have a --setup
parameter which configures defaults in Conf/target.txt, after which
users can change MAX_CONCURRENT_THREAD_NUMBER - instead of the current
method which involves figuring out which of files ends up running
build.exe with '-n <threads>'.
--
Rebecca
next prev parent reply other threads:[~2017-02-23 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 1:20 Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? Rebecca Cran
2017-02-22 4:50 ` Gao, Liming
2017-02-22 5:11 ` Andrew Fish
2017-02-22 5:48 ` Rebecca Cran
2017-02-22 7:35 ` Gao, Liming
2017-02-22 16:34 ` Richardson, Brian
2017-02-22 16:52 ` Rebecca Cran
2017-02-22 19:10 ` Richardson, Brian
2017-02-23 2:49 ` Wei, David
2017-02-23 18:53 ` Brian J. Johnson
2017-02-23 19:10 ` Rebecca Cran [this message]
2017-02-23 23:11 ` Richardson, Brian
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-list 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=e2e07aef-aefa-32da-87bc-60237bf7efa2@bluestop.org \
--to=devel@edk2.groups.io \
/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