All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Using bitbake in minimal chroot environment
Date: Mon, 15 Feb 2010 12:22:56 -0600	[thread overview]
Message-ID: <4B799100.7090203@mwester.net> (raw)
In-Reply-To: <ac9c93b11002150957r4e9bc0e6tbeb56e62c94e89b0@mail.gmail.com>

Frans Meulenbroeks wrote:
> 2010/2/15 Martin Jansa <martin.jansa@gmail.com>:
>>> Seems a good plan to me, please keep us posted.
>>> (actually I've been considering building in a minimalistic VM)
>> Well VM would be much slower..
> 
> Someone else told me the same today.
> What exactly causes this? I would expect I/O to be the differentiating
> factor as memory access and executing instructions should take the
> same time, shouldn't it?

I build in a VM often, and the difference is not very significant.  In
fact, I can't measure the difference in building SlugOS using the wall
clock.

I also tried placing all of my TMPDIR on a tmpfs on my 8GB RAM system,
and building SlugOS -- again, no difference compared to the normal SATA
hard drive for TMPDIR.

So my conclusion is that I/O is not the bottleneck for my OE builds, and
that's the only area where a VM is significantly different in terms of
performance (at least how I use VMs; perhaps other builds may observe
differences).

Before I ended up on my current contract, which locks me away behind
draconian firewalls, I used to take my autobuilder on the road with me
as a VM, building SlugOS and several of the OpenMoko distros -- I
heartily recommend that solution!

-Mike (mwester)



  parent reply	other threads:[~2010-02-15 18:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 13:56 Using bitbake in minimal chroot environment Martin Jansa
2010-02-15 15:24 ` Philip Balister
2010-02-15 16:59   ` Frans Meulenbroeks
2010-02-15 17:19     ` Martin Jansa
2010-02-15 17:57       ` Frans Meulenbroeks
2010-02-15 18:12         ` Martin Jansa
2010-02-15 18:22         ` Mike Westerhof [this message]
2010-02-15 18:36           ` Martin Jansa
2010-02-15 18:43       ` Koen Kooi
2010-02-15 20:53         ` Frans Meulenbroeks
2010-02-15 22:04         ` Tom Rini
2010-02-15 22:15           ` Koen Kooi
2010-02-16  8:11           ` Koen Kooi
2010-02-18  9:20           ` Marcin Juszkiewicz
2010-02-18  9:43             ` Koen Kooi
2010-02-18 13:30             ` Henning Heinold
2010-02-16 13:52 ` Otavio Salvador
2010-02-17  9:35   ` Martin Jansa

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=4B799100.7090203@mwester.net \
    --to=mike@mwester.net \
    --cc=openembedded-devel@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 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.