From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder
Date: Thu, 1 Nov 2012 16:29:14 -0700 [thread overview]
Message-ID: <509305CA.6070103@ti.com> (raw)
In-Reply-To: <CAPnjgZ1XasKxV3QVbOeFR_ooD043LihUgW2JGDJkd5ew5AEusg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/01/12 14:01, Simon Glass wrote:
> Hi Andy / Tom,
>
> On Wed, Oct 31, 2012 at 9:17 PM, Andy Fleming <afleming@gmail.com>
> wrote:
>> On Wed, Oct 31, 2012 at 8:18 PM, Tom Rini <trini@ti.com> wrote:
>>> On Wed, Oct 31, 2012 at 05:11:51PM -0700, Simon Glass wrote:
>>>
>>> [snip]
>>>> Also rather than running with 'make -j40' or whatever, it
>>>> uses 'make -j1' but with 40 threads. This increases CPU
>>>> utilisation quite substantially (almost 50%) - I think this
>>>> was discussed some time ago,
>>>
>>> MAKEALL supports this, but doesn't default to it, today. I'm
>>> wondering if we ought to make it the default for all non-single
>>> board builds. The winning point is right around
>>> boards-to-build == `grep -c processor /proc/cpuinfo` and I
>>> think is right around setting NBUILDS to that value, both on
>>> consumer multicore and heavy-duty 32/64 core boxes.
>>
>> Yeah, I usually set BUILD_NBUILDS to 24-50 on my 24-thread
>> system, and then set BUILD_NCPUS to 1-4. It's nice to offer a
>> little bit of parallelism on the individual builds, sometimes. I
>> did a bunch of tests, but not in a scientific fashion. Enough to
>> agree with you that maxing out builds seems to win for u-boot.
>
> As a bit of an unscientific test, what sort of time does it take
> to build all 1000-or-so boards on your systems?
My setup using MAKEALL does 921 boards (arm/powerpc/mips) with ELDK
5.2 in 54min wall-clock with 397% CPU util (on a 6 core machine).
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQkwXKAAoJENk4IS6UOR1Ws+oP/A2Estr8LHk2zt3cclDrshwI
9iNpiMvwJ2a/Qj3DzK6q3tuLKIJq/Chfsgczrz3wlv6RGqN5SB8U/Cbl9/OAg9oC
jmSEjpGxT3pJyRKscyf/78cjMb06BadHVybPjkMtmfdlay3+H4CLLFkVahM1BKut
+7MxTFtQIkPkHtXUwcTSYXuIhwwz61d6R65colHoHWVIbtRWpksaWa64107mEg3K
0A4Ite+FYoMK0BeswA1mPGknDCCLfgE32oXI4k4tQBAXrLcYWKlxLcirGydiZ46l
Mrqh+62EA4U2FEVj3VbRjB2JtqRiqtbYYNSk9fwkdU0Fa/eYZacYYxStZVnVTfaQ
RgZd0Gq7knJUed8bS0RvptDKLnMCadc0CgVEQ6Svj2JgfeZ9l/HOJkUX/MI7bCmv
eKrtQQium4cJfXx2fGGdR2O21g+oQML/V0UTHkq78qMr3Z9Bqj3wRRyVGc5ch7kb
3P8aYjlJG8qU6OtDiwvRNIMvAQzovetJu18L+F/X3lgxqsvrEjk1Ugdach0smmkl
TcM9U21la7oOAxhFg4J5W6aatdDx6kKU6s4K68kpcvpQ0MJjQ6bhjKASzf/VFuTl
6vLXUiN+qHc/2yBmuxgMluRfAzFEsLWZ3Y6r3bQC4f3mfmUZxt7CJ8D+rYqSQKUW
TDHABRVdUDJxbypUaA8q
=VhSN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-11-01 23:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 21:25 [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Simon Glass
2012-10-31 21:25 ` [U-Boot] [PATCH 2/2] WIP: Test version of buildman - U-Boot builder Simon Glass
2012-10-31 22:46 ` Wolfgang Denk
2012-10-31 22:51 ` Tom Rini
2012-10-31 23:08 ` Simon Glass
2012-10-31 23:37 ` Wolfgang Denk
2012-11-01 0:11 ` Simon Glass
2012-11-01 1:18 ` Tom Rini
2012-11-01 4:17 ` Andy Fleming
2012-11-01 21:01 ` Simon Glass
2012-11-01 23:29 ` Tom Rini [this message]
2012-12-01 20:55 ` Simon Glass
2012-10-31 22:42 ` [U-Boot] [PATCH 1/2] WIP: Changes to patman libraries Wolfgang Denk
2012-10-31 23:12 ` Simon Glass
2012-10-31 23:40 ` Wolfgang Denk
2012-11-01 0:04 ` Simon Glass
2012-11-01 20:59 ` Simon Glass
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=509305CA.6070103@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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