From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libc-locale: split locale handling from libc recipe.
Date: Thu, 09 Jun 2011 12:43:18 +0100 [thread overview]
Message-ID: <1307619798.2529.4844.camel@phil-desktop> (raw)
In-Reply-To: <1307618944.15712.150.camel@rex>
On Thu, 2011-06-09 at 12:29 +0100, Richard Purdie wrote:
> As you can see, eglibc do_package takes about 14 minutes which is about
> 14% of our build time. That is a long time to block pretty much all
> packaging activity, particularly if you have access to something with
> several cores. When it does complete, even on my 4 core system you see a
> "stampeding herd" of packaging happening on the build charts suggesting
> a backlog does build up.
Yeah, I can imagine that a backlog of packaging activity does build up.
The thing I'm not entirely clear on is whether this is actually causing
some threads to get starved of work (and hence the total build time to
be longer than it needs to be) or whether we're really just shifting
things around in the timeline without making much/any difference to the
overall build duration. (I'm not familiar enough with bitbake's
scheduler to know whether it will schedule tasks as early as possible,
or as late as possible, or something else.)
Just as a matter of interest, are you using qemu-based locale generation
or the cross localedef for your measurement? 14 minutes does sound like
an awfully long time and I wonder whether there is anything we could do
in absolute terms to just speed that process up.
p.
next prev parent reply other threads:[~2011-06-09 11:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 9:08 [PATCH 0/1][RFC] libc locale split Dongxiao Xu
2011-06-08 9:08 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-08 9:36 ` Phil Blundell
2011-06-08 15:35 ` Richard Purdie
2011-06-09 11:14 ` Phil Blundell
2011-06-09 11:29 ` Richard Purdie
2011-06-09 11:43 ` Phil Blundell [this message]
2011-06-09 13:15 ` Richard Purdie
2011-06-09 13:51 ` Richard Purdie
2011-06-09 13:53 ` Koen Kooi
2011-06-09 13:55 ` Phil Blundell
-- strict thread matches above, loose matches on Subject: below --
2011-06-22 9:01 [PATCH 0/1 v2][PULL] libc locale split Dongxiao Xu
2011-06-22 9:01 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-22 11:44 ` Phil Blundell
2011-06-23 4:08 ` Xu, Dongxiao
2011-06-23 9:40 ` Phil Blundell
2011-06-23 10:14 ` Richard Purdie
2011-06-23 23:42 ` Khem Raj
2011-06-27 5:49 ` Xu, Dongxiao
2011-06-22 14:44 ` Khem Raj
2011-06-22 14:47 ` Phil Blundell
2011-06-22 15:17 ` Mark Hatle
2011-06-22 15:43 ` Khem Raj
2011-06-27 8:37 [PATCH 0/1 v3][PULL] libc locale split Dongxiao Xu
2011-06-27 8:37 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-27 8:58 ` Phil Blundell
2011-06-28 0:51 ` Xu, Dongxiao
2011-06-28 9:07 ` Phil Blundell
2011-06-28 11:07 ` Richard Purdie
2011-06-28 12:17 ` Koen Kooi
2011-06-28 14:00 ` Richard Purdie
2011-06-28 19:37 ` Koen Kooi
2011-06-28 20:15 ` Koen Kooi
2011-06-28 4:12 ` Xu, Dongxiao
2011-07-08 14:55 ` Phil Blundell
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=1307619798.2529.4844.camel@phil-desktop \
--to=pb@pbcl.net \
--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