All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: Can anything be done about do_rootfs speed?
Date: Wed, 28 Aug 2013 09:20:25 +0200	[thread overview]
Message-ID: <20130828072025.GC3544@jama> (raw)
In-Reply-To: <8EB78E64DFE9436EAFB462E357C464EC@PAULD>

[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]

On Tue, Aug 27, 2013 at 05:10:42PM -0700, Paul D. DeRocco wrote:
> > From: Gary Thomas
> > 
> > As far as I understand, the 'do_rootfs' step in building an 
> > image is basically
> > equivalent to running "${PKG_MGR} install 
> > <all_required_packages>", where PKG_MGR
> > is your package management method of choice - ipk or rpm.  
> > This seems to me to
> > be a very single-threaded process.
> 
> If there's a way to command the package manager to install a package
> without enforcing dependencies (Is that what opkg --nodeps does?), then
> couldn't the package manager be invoked on one package at a time in n
> threads, just like the other tasks are now run? I don't really have any
> sense of how long it takes to install the packages, as opposed to building
> the final tarball or hddimage and applying the permissions from the pseudo
> database, which would certainly be single-threaded.
> 
> > Perhaps you should think more about how you are using this.  
> > If you don't need
> > to rebuild the whole image every time, maybe you can use the 
> > package management
> > tools instead?  For example, I routinely build images as well 
> > but I also try to
> > use 'opkg' as much as possible to manage package updates, 
> > etc.   This is a huge
> > time saver, especially when making small or incremental 
> > changes.  I only rely
> > on the full image builds when I want to "checkpoint" the 
> > state of the system.
> 
> I'd like to try that, but I'm not sure how. If I've tweaked one recipe,
> how do I get it to build it and package it, and then stop? Do I use
> "bitbake -c package"? And then do I use "opkg -d" to manually install it
> directly onto my SD card? If my rootfs is a loop mounted hddimage in a
> FAT16 file (as it is on my Atom project), do I loop mount it on my build
> system and install into that?
> 
> Installing directly to the card would be nice because copying the whole
> damn rootfs to the card takes an annoying amount of time, too.

Are you sure that you're not building some unnecessary IMAGE_FSTYPES?
Last time someone asked my why it takes so long I've added some debug
output to do_rootfs and found out that only half of the time was opkg
installing packages and the rest was various IMAGE_FSTYPES.

e.g. tar.bz2 takes very long without pbzip2 or lbzip2

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-08-28  7:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 22:27 Can anything be done about do_rootfs speed? Paul D. DeRocco
2013-08-27 23:25 ` Gary Thomas
2013-08-28  0:10   ` Paul D. DeRocco
2013-08-28  7:20     ` Martin Jansa [this message]
2013-08-28  8:36       ` Paul D. DeRocco
2013-08-28  8:49         ` Samuel Stirtzel
2013-08-28 11:30           ` Samuel Stirtzel
2013-09-04 23:50             ` Paul D. DeRocco
2013-09-05  6:56               ` Nicolas Dechesne
2013-08-28 10:55     ` Gary Thomas
2013-08-28 11:29       ` Paul Barker
2013-09-02 12:26       ` Burton, Ross
2013-10-02 16:37       ` Trevor Woerner
2013-10-02 19:20         ` Gary Thomas

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=20130828072025.GC3544@jama \
    --to=martin.jansa@gmail.com \
    --cc=pderocco@ix.netcom.com \
    --cc=yocto@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 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.