Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: What's taking so long??
Date: Thu, 20 Jan 2011 08:11:47 -0700	[thread overview]
Message-ID: <4D3850B3.2030100@mlbassoc.com> (raw)

My target platform/distro uses IPK and I have a local kernel
recipe which is based on the pre linux-yocto recipe that was
used by Poky.  When I build & package the kernel, I have
terrible performance - this is new, it used to be just fine.

Here's what I mean.  Building for my kernel and timing the
various steps, e.g.
   % time bitbake virtual/kernel -c compile

My kernel:
   compile            1m49s
   deploy             0m16s
   populate_sysroot   0m38s
   package           23m20s

Just to compare, using OTS Poky for BeagleBoard:
   compile            5m07s
   deploy             0m36s
   populate_sysroot   0m29s
   package            5m02s

That's a five-fold difference in the time to build & package
the kernel.

What am I doing [wrong?] that makes this so?
Would it be better if I switched to RPM like the BB is using?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2011-01-20 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 15:11 Gary Thomas [this message]
2011-01-20 15:58 ` What's taking so long?? Joshua Lock
2011-01-20 16:02   ` Gary Thomas
2011-01-20 16:04   ` Koen Kooi
2011-01-20 16:34     ` Gary Thomas
2011-01-20 16:40       ` Gary Thomas
2011-01-21 14:14         ` Richard Purdie
2011-01-21 14:10 ` Richard Purdie
2011-01-21 14:25   ` Gary Thomas
2011-01-21 16:17     ` Richard Purdie
2011-01-21 20:48       ` Gary Thomas
2011-01-22 17:44         ` Gary Thomas
2011-01-28  7:42           ` Xu, Dongxiao
2011-01-28  7:49             ` Tian, Kevin
2011-02-08 18:06               ` Richard Purdie
2011-01-28 10:34             ` Richard Purdie

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=4D3850B3.2030100@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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