All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Using bitbake in minimal chroot environment
Date: Mon, 15 Feb 2010 23:15:59 +0100	[thread overview]
Message-ID: <hlch2u$o8p$1@ger.gmane.org> (raw)
In-Reply-To: <1266271477.31865.4.camel@trini-m4400>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15-02-10 23:04, Tom Rini wrote:
> On Mon, 2010-02-15 at 19:43 +0100, Koen Kooi wrote:
> 
> [snip]
>> On a recent intel/amd cpu VMs I can't measure much difference between VM
>> and non-vm builds.
>> My main buildmachine at work is an ubuntu 8.04LTS vm running under
>> windows XP. The only major speedup I can get building in a native
>> install would be using 64bit, since the VM is 32 bit, but it does expose
>> both CPU cores :)
> 
> What are you (and everyone else saying it's fine) running the VM with?
> I've got people reporting just unusable build times inside VMs on what
> should be reasonable hardware.  That said, I've profiled some builds and
> seen that IO is not a bottleneck (stuff like waiting for virtual/libc to
> stage and gcc-cross to get populated is).

I'm using virtualbox on a Dell D630 (core2duo, 4GB of ram) laptop. I
managed to cut 2 hours (yes, hours) of the buildtime by moving lots of
stuff to new style staging. With a big tmpdir (6 machines, 2 different
archs, lots of machine specific stuff) old-style staging takes eons to
stat every file and build a list.
Using virtualbox on a 2GB osx machine isn't running so hot because OSX
seems to go out of its way to put the VM in swap instead of ram :(

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLecefMkyGM64RGpERAmLWAJ0dsBhzCnV86Z/rxJKVVGMUS+4q2wCfTPZb
ykkNNSvTlPN2ZEIQT8xgfqY=
=PZD0
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-02-15 22:19 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
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 [this message]
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='hlch2u$o8p$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.