From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] GNU/Linux/Plan 9 disto
Date: Mon, 11 Jul 2011 14:12:02 -0400 [thread overview]
Message-ID: <088ac8dca18ec9ef9e83f70f167982eb@coraid.com> (raw)
In-Reply-To: <CAFSF3XO7ejhGBq5Zqj1oL7UnnPf7naTtwbG56hN4k1fz3koxBw@mail.gmail.c>
On Mon Jul 11 13:58:27 EDT 2011, 23hiro@googlemail.com wrote:
> > I'd certainly like something where my local processes migrate from
> > my lower powered laptop including the Window manager migrate to a
> > more powerful CPU when it becomes available and back again when my
> > laptop becomes disconnected,
> >
> Here network latency is too high for such small tasks nowadays solved
> by CPUs. If you have to wait for your CPU in the 21st century you're
> doing it wrong.
maybe in this particular case. here are two others where i think
using more powerful cpus and/or networks might make a lot of sense.
- suppose you have a really low powered device that is sometimes docked.
- suppose you want to run fluid dynamics on your phone. if you want
to make it run faster, you import some resources from a computing resource
like ec2.
it's true that network latency is a huge deal these days. and even a multicore
machine looks like a bunch of fast cores connected to their l3 and each other
by a slow network. but if you have a "large enough" packet of work, it can make
sense to move it over to another cpu. i don't see why given an apropriate defn
of "large enough" this couldn't work across different orders of magnitude.
- erik
next prev parent reply other threads:[~2011-07-11 18:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 16:05 rbnsw-plan9
2011-07-11 16:41 ` Jens Staal
2011-07-11 16:59 ` Gorka Guardiola
2011-07-11 19:31 ` Charles Forsyth
2011-07-12 5:59 ` Pavel Zholkover
2011-07-12 15:13 ` [9fans] Plan 9 Go (Was: GNU/Linux/Plan 9 disto) Lucio De Re
2011-07-12 18:35 ` Francisco J Ballesteros
2011-07-13 18:31 ` Lucio De Re
2011-07-13 18:45 ` Lucio De Re
2011-07-14 18:59 ` stephano zanzin
2011-07-14 20:21 ` Lucio De Re
2011-07-14 20:35 ` Iruatã Souza
2011-07-15 2:37 ` Fazlul Shahriar
2011-07-22 4:40 ` Lucio De Re
2011-07-22 14:37 ` Ethan Grammatikidis
2011-07-27 2:55 ` kokamoto
2011-07-12 18:44 ` Skip Tavakkolian
2011-07-12 12:35 ` [9fans] GNU/Linux/Plan 9 disto Ethan Grammatikidis
2011-07-12 5:50 ` Jens Staal
[not found] ` <CACm3i_j1dxqY=sfunozAXRY+uhO83BnTodfpWvNb+4rSNouC_g@mail.gmail.c>
2011-07-11 17:43 ` erik quanstrom
2011-07-11 19:29 ` Charles Forsyth
2011-08-21 16:20 ` Enrico Weigelt
2011-08-21 17:27 ` erik quanstrom
2011-08-21 16:16 ` Enrico Weigelt
2011-07-11 17:56 ` hiro
[not found] ` <CAFSF3XO7ejhGBq5Zqj1oL7UnnPf7naTtwbG56hN4k1fz3koxBw@mail.gmail.c>
2011-07-11 18:12 ` erik quanstrom [this message]
2011-07-12 0:10 ` hiro
2011-07-12 13:35 ` Ethan Grammatikidis
2011-07-12 17:18 ` hiro
2011-07-12 18:09 ` Richard Miller
2011-07-12 19:08 ` Ethan Grammatikidis
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=088ac8dca18ec9ef9e83f70f167982eb@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).