All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
Cc: yocto <yocto@yoctoproject.org>, Chris Larson <clarson@kergoth.com>
Subject: Re: Bitbake and task offloading onto multiple cloud-based servers
Date: Wed, 09 Jan 2013 09:43:25 -0600	[thread overview]
Message-ID: <1357746205.1532.5.camel@empanada> (raw)
In-Reply-To: <50ED5B6D.4080303@dynamicdevices.co.uk>

On Wed, 2013-01-09 at 11:58 +0000, Alex J Lennon wrote:
> > In the 1.1 timeframe I proposed something similar for a demo/research
> > project - I'll just copy the proposal verbatim below in case any of the
> > ideas could be of any value.  
> 
> Very interesting Tom. Thanks for your thoughts.
> 
> 
> > if throwing a
> > 40-processor system at a build doesn't really help much it's not likely
> > to be of much help either to distribute the individual pieces out to the
> > 'cloud'.
> 
> Are there any figures for build time versus increase in processor cores?
> It would be interesting to see what the immediate performance gain is
> for a build with a low number of additional cores and then where it tops
> out?

These threads have some hard data:

https://lists.yoctoproject.org/pipermail/poky/2011-July/006802.html
https://lists.yoctoproject.org/pipermail/yocto/2012-April/008293.html

Some of which is summarized here:

https://wiki.yoctoproject.org/wiki/Build_Performance

Other people may have pointers to more data or summaries..

Tom

> 
> > The whole
> > process is completely peer-to-peer with no single node in charge - in
> > that context, a more appropriate name for it might be 'BuildTorrent'.
> 
> A "BuildTorrent". I like it!
> 
> Cheers,
> 
> Alex
> 




  reply	other threads:[~2013-01-09 15:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-24  7:37 Fails to launch the hob Biao
2012-12-24 12:23 ` Mihai Lindner
2012-12-24 12:37   ` Mihai Lindner
2012-12-25  6:16     ` Biao
2013-01-03 16:47       ` Barros Pena, Belen
2013-01-03 23:11         ` Zhang, Jessica
2013-01-04 10:10           ` Barros Pena, Belen
2013-01-04 16:57           ` Barros Pena, Belen
2013-01-04 20:56         ` Bitbake and task offloading onto multiple cloud-based servers Alex J Lennon
2013-01-04 21:08           ` Chris Larson
2013-01-04 21:17             ` Alex J Lennon
2013-01-04 21:27               ` Chris Larson
2013-01-08 23:12               ` Tom Zanussi
2013-01-09 11:58                 ` Alex J Lennon
2013-01-09 15:43                   ` Tom Zanussi [this message]
2013-01-04 22:43           ` Mark Hatle
2013-01-04 22:47             ` Alex J Lennon
2013-01-04 23:14               ` Flanagan, Elizabeth

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=1357746205.1532.5.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=ajlennon@dynamicdevices.co.uk \
    --cc=clarson@kergoth.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.