From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Fri, 6 Jun 2014 11:31:48 -0500 [thread overview]
Message-ID: <20140606113148.464ff3c8@core2quad.morethan.org> (raw)
In-Reply-To: <CAE9DZURp2teR8p5WP3OQEZyZ71qD=8U97q03cRd0yHbTsz8FwA@mail.gmail.com>
On Fri, 6 Jun 2014 11:14:15 -0500
Dallas Clement <dallas.a.clement@gmail.com> wrote:
> > Seems a fairly decent setup. You have enough RAM, and a good storage
> > system (ideally based on SSDs) ?
>
> Yep, very speedy SSDs and 64 GB for RAM. Because of all the
> serialization in this build process,
> building from a large ram disk seems to make little difference.
>
Having 7 of your 8 cores sitting in their idle loop is probably your
#1 thing to address. . . .
With a very large selection of packages, perhaps you could split them
into several (8, 9?) Buildroot trees.
Then run those buildroot instances as jobs at the same time.
Or...
At least pull the really big time consumers out, into their own BR
instance, and use your idle cores on those.
Mike
next prev parent reply other threads:[~2014-06-06 16:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 16:34 [Buildroot] autoconf caching Dallas Clement
2014-06-05 17:05 ` Baruch Siach
2014-06-05 17:34 ` Yann E. MORIN
2014-06-05 17:39 ` Dallas Clement
2014-06-05 18:57 ` Yann E. MORIN
2014-06-05 20:42 ` Thomas Petazzoni
2014-06-05 22:06 ` Dallas Clement
2014-06-06 6:13 ` Thomas Petazzoni
2014-06-06 7:15 ` Thomas Petazzoni
2014-06-06 16:14 ` Dallas Clement
2014-06-06 16:31 ` Mike Zick [this message]
2014-06-06 16:45 ` Dallas Clement
2014-06-10 9:32 ` Fabio Porcedda
2014-06-11 17:41 ` Dallas Clement
2014-06-13 9:23 ` Fabio Porcedda
2014-06-14 0:52 ` Dallas Clement
2014-06-14 7:57 ` Thomas Petazzoni
2014-06-18 12:37 ` Fabio Porcedda
2014-06-07 9:04 ` Thomas Petazzoni
2014-06-08 8:19 ` [Buildroot] [UNSURE]Re: " François Perrad
2014-06-09 20:10 ` Dallas Clement
2014-06-10 7:25 ` Thomas Petazzoni
2014-06-06 5:20 ` [Buildroot] " Waldemar Brodkorb
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=20140606113148.464ff3c8@core2quad.morethan.org \
--to=minimod@morethan.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