From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Inefficient find of pkg data
Date: Wed, 30 May 2012 16:21:05 -0700 [thread overview]
Message-ID: <cover.1338419593.git.elizabeth.flanagan@intel.com> (raw)
[YOCTO #2419]
find -name is a horrible way to find files (.025s per exec). Changing this
to shell expansion (.002 per exec). Also, no point in having a big for loop when
I pipe this into head anyway.
I tried this a few ways and this seems the most efficient reducing rootfs
generation down to around 30s from around 50s.
The following changes since commit 348da93e283b2b8454fd9cde80d4b17378e2a168:
webkit-gtk: Use glib as unicode backend to avoid browser crash (2012-05-30 17:38:02 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib eflanagan/license_1.3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=eflanagan/license_1.3
Elizabeth Flanagan (1):
license.bbclass: optimize pkg runtime data
meta/classes/license.bbclass | 40 +++++++++++++++++++---------------------
1 files changed, 19 insertions(+), 21 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-05-30 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 23:21 Elizabeth Flanagan [this message]
2012-05-30 23:21 ` [PATCH 1/1] license.bbclass: optimize pkg runtime data Elizabeth Flanagan
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=cover.1338419593.git.elizabeth.flanagan@intel.com \
--to=elizabeth.flanagan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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