From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2019.02 performance
Date: Mon, 11 Mar 2019 21:59:03 +0000 [thread overview]
Message-ID: <1552341542.7410.20.camel@impinj.com> (raw)
With 2018.02, I had to disable the package size and related hooks as
they were too slow: over half the build time. As I'm sure some
remember, there was a thread about it and performance was
improved. Here's the results with 2019.02. I'm using a real config
for a product we have and testing on a reasonably modern native Linux
workstation with a decent NVMe SSD and a four core processor. Using
ccache, which had already built the software.
Total build time: real 22:53, CPU 39:04.
Breakdown by build step (host/stage/target/images mean install same),
across all packages:
configure 666.223
build 381.480
host 122.191
extract 57.489
target 57.039
stage 28.356
patch 9.711
postimage 9.008
finalize 6.396
images 0.063
download 0.022
The single threaded configure and cmake scripts remain the killer,
through total of all install steps is about 2/3 of the build step time.
Breakdown for the global instrumentation hooks, across all packages and
build steps:
check_host_rpath 64.345
step_pkg_size 32.992
check_bin_arch 26.286
step_check_build_dir 8.365
step_time 7.895
pkg_size is much more reasonable now. In total, these are about 10.2%
of the total build time.
Next are benchmarks from a cloud VM, which is considerably slower.
Total build time: Real 53:58, CPU 55:22
configure 1021.933
build 936.449
host 206.171
extract 106.642
target 98.028
stage 53.747
finalize 40.840
download 25.091
postimage 22.876
patch 19.153
images 0.119
The GIH breakdown:
check_host_rpath 117.981
step_pkg_size 49.881
check_bin_arch 46.035
step_time 12.573
step_check_build_dir 9.307
About 7.2% of total build time.
next reply other threads:[~2019-03-11 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:59 Trent Piepho [this message]
2019-03-12 8:05 ` [Buildroot] 2019.02 performance Thomas Petazzoni
2019-03-12 9:57 ` Arnout Vandecappelle
2019-03-12 20:30 ` 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=1552341542.7410.20.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