Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky <poky@yoctoproject.org>
Subject: Re: Quick hack for profiling tasks
Date: Thu, 03 Feb 2011 11:22:03 +0000	[thread overview]
Message-ID: <1296732123.1544.8429.camel@rex> (raw)
In-Reply-To: <1296656936.1544.3387.camel@rex>

On Wed, 2011-02-02 at 14:28 +0000, Richard Purdie wrote:
> On Tue, 2011-02-01 at 09:38 -0600, Mark Hatle wrote:
> > I'm still used to the RPM world where locales are included in the main package
> > and "tagged" so they will or won't be included automatically.  I forget they are
> > separated out in Poky by default.
> > 
> > So skipping them makes sense to me...
> 
> Some further numbers to backup my comments:
> 
> "time bitbake poky-image-sato -k"
> 
> Before patch:
> 
> real 129m40.482s
> user 480m16.520s
> sys 66m9.170s
> 
> After patch:
> 
> real 117m7.704s
> user 455m40.330s
> sys 55m1.390s

and just for reference, with the recent fetcher improvements:

real	113m39.607s
user	458m25.570s
sys	55m15.250s

I'm doubting the accuracy of the user figure there but the build should
be faster overall due to less taring/untaring of tarballs and it looks
like it is. It would be possible to really show an improvement by
specifically profiling the kernel/linux-libc-headers recipes.

Cheers,

Richard



      reply	other threads:[~2011-02-03 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  0:28 Quick hack for profiling tasks Richard Purdie
2011-02-01  0:40 ` Richard Purdie
2011-02-01  1:43   ` Mark Hatle
2011-02-01 11:05     ` Richard Purdie
2011-02-01 15:38       ` Mark Hatle
2011-02-02 14:28         ` Richard Purdie
2011-02-03 11:22           ` Richard Purdie [this message]

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=1296732123.1544.8429.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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