From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Tom Zanussi <tom.zanussi@intel.com>
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 11:58:37 +0000 [thread overview]
Message-ID: <50ED5B6D.4080303@dynamicdevices.co.uk> (raw)
In-Reply-To: <1357686756.2515.50.camel@empanada>
> 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?
> 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
next prev parent reply other threads:[~2013-01-09 11:58 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 [this message]
2013-01-09 15:43 ` Tom Zanussi
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=50ED5B6D.4080303@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=clarson@kergoth.com \
--cc=tom.zanussi@intel.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.