From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Speeding up builds
Date: Mon, 04 Nov 2013 20:06:21 +0100 [thread overview]
Message-ID: <5d58cf72-cd29-4f75-b348-4b59b4941a2f@email.android.com> (raw)
In-Reply-To: <CAE9DZUT-G8g5cwWamULZ2ppUSOHjNf1O35diTno-uZj1_tCggA@mail.gmail.com>
Hi Dallas,
Dallas Clement <dallas.a.clement@gmail.com> wrote:
>Hi All,
>
>I'm just looking for some tips on how to speed up my build times. My
>rootfs contains many packages with lots of dependencies. Even with 8 fast
>Xeon cores, 64GB of RAM, SSDs, and SAS drives, my builds are taking 1 hour
>and 50 minutes.
>
>When I observe CPU utilization with htop, I rarely see more than one CPU
>core getting worked hard. Occasionally, I will see all 8 cores maxed at
>100%.
>
>make -j 16 seems to make little difference.
>
>What can I do to get all my CPU cores working all the time?
What is the value of BR2_JLEVEL in your .config?
And have you tried enabling ccache?
What takes a significant amount of time are the configure steps of all packages, which are not parallelized.
Best regards,
Thomas
next prev parent reply other threads:[~2013-11-04 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 19:00 [Buildroot] Speeding up builds Dallas Clement
2013-11-04 19:06 ` Thomas De Schampheleire [this message]
2013-11-04 19:41 ` Dallas Clement
2013-11-04 19:50 ` Thomas De Schampheleire
2013-11-04 20:11 ` Dallas Clement
2013-11-04 23:15 ` Dallas Clement
2013-11-04 23:19 ` Thomas Petazzoni
2013-11-04 23:20 ` Thomas Petazzoni
2013-11-04 23:38 ` Dallas Clement
2013-11-04 23:48 ` Peter Korsgaard
2013-11-05 17:29 ` Dallas Clement
2013-11-05 17:48 ` Thomas De Schampheleire
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=5d58cf72-cd29-4f75-b348-4b59b4941a2f@email.android.com \
--to=patrickdepinguin@gmail.com \
--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