From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build time increase in 2018.02
Date: Sat, 10 Mar 2018 01:14:13 +0000 [thread overview]
Message-ID: <1520644453.25567.398.camel@impinj.com> (raw)
We've seen a big increase in build time with the latest buildroot. On
a vpshere instance, times have gone up from 45 minutes to 180+ minutes.
I think there are some issues with poor vm performance that can be
addressed outside of buildroot, but even on a real Linux workstation,
there's been a significant increase in time.
Here's a breakdown of build time by task for a build that takes 26.5
minutes. ccache is in use and is quite effectively decreasing the
compile time. I've split out all the instrumentation steps so they can
be accounted separately from the rest of host-install, etc. In this
list, host-install only includes the time spent executing the install
commands, not instrumentation or pre/post-hooks.
step_pkg_size 831.17
configure 441.77
build 149.56
extract 40.28
host-install 31.96
all other 27.78
check_host_rpath 20.86
check_bin_arch 20.77
target-install 19.84
stage-install 13.25
Finding the package sizes takes more time than everything else put
together. And indeed, if I remove that step, check_bin_arch, and fake
out check-uniq-files, the build drops from 26.5 minutes to 12 minutes!
If we consider config+buid+extract+*-install to be the actual package
building and the rest overhead, then the build is about %56 overhead
and %44 building. And most of the building time is (re-)running
autoconf scripts.
On the vsphere instance, the time is much much worse. I'm still
waiting for numbers. It takes hours. I think the lousy vm filesystem
performance magnifies the problem.
next reply other threads:[~2018-03-10 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 1:14 Trent Piepho [this message]
2018-03-10 11:32 ` [Buildroot] Build time increase in 2018.02 Peter Korsgaard
2018-03-12 18:27 ` Trent Piepho
2018-03-12 18:53 ` Peter Korsgaard
2018-03-12 20:08 ` Yann E. MORIN
2018-03-13 19:09 ` Trent Piepho
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=1520644453.25567.398.camel@impinj.com \
--to=tpiepho@impinj.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