From: Saul Wold <saul.wold@intel.com>
To: "poky >> \"poky@o-hand.com\"" <poky@o-hand.com>
Subject: Rough timing of rpm vs opkg rootfs builds
Date: Thu, 11 Nov 2010 14:30:49 -0800 [thread overview]
Message-ID: <4CDC6E99.4030709@intel.com> (raw)
Mark, Qing, Dongxiao:
Richard and I were talking the other day and I started a little
experiment with checking the timing of RPM rootfs build vs OPKG. For the
minimal and SDK images:
Minimal - OPKG
real 1m39.456s
user 1m18.693s
sys 0m4.188s
SDK - OPKG
real 10m50.784s
user 6m8.059s
sys 0m51.523s
Minimal - RPM
real 4m25.166s
user 6m14.503s
sys 0m27.534s
SDK - RPM
real 24m40.979s
user 7m29.856s
sys 4m25.561s
Clearly there is some work we can do with RPM, which takes more than
double the time, yes, I know it's doing more work, but maybe there are
some optimizations that can be done to improve the speed.
For the autobuilder, we build 7 SDK images, which is about 3 hours using
RPM vs about 75 minutes for OPKG, the Sato and LSB images are not much
faster so this is another place we should be looking to help our build time.
This is just another place for us to open dialog and figure out what's
going on.
Sau!
next reply other threads:[~2010-11-11 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 22:30 Saul Wold [this message]
2010-11-12 4:58 ` Rough timing of rpm vs opkg rootfs builds Richard Purdie
2010-11-12 15:12 ` R P Herrold
2010-11-14 17:28 ` Richard Purdie
2010-11-15 21:14 ` Mark Hatle
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=4CDC6E99.4030709@intel.com \
--to=saul.wold@intel.com \
--cc=poky@o-hand.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.