From: matt <maht-9fans@maht0x0r.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Barrelfish
Date: Wed, 28 Oct 2009 15:37:23 +0000 [thread overview]
Message-ID: <4AE86533.3020706@maht0x0r.net> (raw)
In-Reply-To: <20091021154323.GA10118@nipl.net>
Sorry to kick this rotting horse but I just got back
>
>
>>You've got to feed in 2 hours of source material - 820Gb per stream, how?
>>
>>
>
>I suppose some sort of parallel bus of wires or optic fibres.
>
we call that "hand waving"
>If I have
>massively parallel processing I would want massively parallel IO to go with it.
>I.e. something like "read data starting from here" -> "here it is streaming one
>megabit in parallel down the bus at 1Ghz over 1 million channels"
>
>
While riding a unicorn
>would take advantage of perhaps 720 "cores" to encode a two hour video in 10
>second chunks with barely any Ahmdal effects,
>
>
This 720Gbit storage device sounds pretty good.
>People do this stuff every day.
>Have you heard of a render-farm?
>
>
Your sarcasm is cute. Have you used a render farm ? You're right that
rendering on a few cores is CPU bound. But you've moved the goalposts by
100,000,000 orders of magnitude.
We have this comic on the wall with "programmer|compiling" replaced with
"animator|rendering"
http://xkcd.com/303/
And there's a standing order that you can't have sex unless you're
rendering.
>I'm not sure why I'm wasting time writing about this, it's obvious anyway.
>
>
Yeah, that must be why everyone is rendering Imax movies in a few seconds.
We can all imagine a place where computation is instant and we just say
"computer! run Sherlock Holmes on the Holodeck from where we left off,
but this time give it a Wild West theme".
next prev parent reply other threads:[~2009-10-28 15:37 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20091015105328.GA18947@nipl.net>
2009-10-15 13:27 ` erik quanstrom
2009-10-15 13:40 ` Richard Miller
2009-10-16 17:20 ` Sam Watkins
2009-10-16 18:18 ` Latchesar Ionkov
2009-10-19 15:26 ` Sam Watkins
2009-10-19 15:33 ` andrey mirtchovski
2009-10-19 15:50 ` ron minnich
2009-10-16 21:17 ` Jason Catena
2009-10-17 20:58 ` Dave Eckhardt
2009-10-18 2:09 ` Jason Catena
2009-10-18 16:02 ` Dave Eckhardt
2009-10-17 18:45 ` Eris Discordia
2009-10-17 21:07 ` Steve Simon
2009-10-17 21:18 ` Eric Van Hensbergen
2009-10-18 8:48 ` Eris Discordia
2009-10-18 8:44 ` Eris Discordia
2009-10-19 15:57 ` Sam Watkins
2009-10-19 16:03 ` ron minnich
2009-10-19 16:46 ` Russ Cox
2009-10-20 2:16 ` matt
2009-10-20 9:15 ` Steve Simon
2009-10-21 15:43 ` Sam Watkins
2009-10-21 16:11 ` Russ Cox
2009-10-21 16:37 ` Sam Watkins
2009-10-21 18:01 ` ron minnich
2009-10-28 15:37 ` matt [this message]
[not found] ` <A90043D02D52B2CBF2804FA4@192.168.1.2>
2009-10-18 0:06 ` ron minnich
2009-10-18 0:54 ` Roman Shaposhnik
[not found] <<4ADD147A.4090801@maht0x0r.net>
2009-10-20 2:11 ` erik quanstrom
2009-10-20 2:33 ` matt
[not found] <<20091019182352.GA1688@polynum.com>
2009-10-19 18:48 ` erik quanstrom
[not found] <<4ADC7439.3060502@maht0x0r.net>
2009-10-19 16:13 ` erik quanstrom
2009-10-19 18:23 ` tlaronde
2009-10-20 1:38 ` matt
2009-10-20 1:58 ` Eris Discordia
2009-10-20 2:17 ` matt
[not found] <<20091019155738.GB13857@nipl.net>
2009-10-19 16:05 ` erik quanstrom
2009-10-19 16:34 ` Sam Watkins
2009-10-19 17:30 ` ron minnich
2009-10-19 17:57 ` W B Hacker
2009-10-19 18:14 ` David Leimbach
[not found] <<20091018031508.717CE5B30@mail.bitblocks.com>
2009-10-19 13:44 ` erik quanstrom
2009-10-19 14:36 ` David Leimbach
[not found] <<d50d7d460910161417w45b5c675p8740315aaf6861f@mail.gmail.com>
2009-10-16 22:25 ` erik quanstrom
[not found] <<20091016172030.GB3135@nipl.net>
2009-10-16 18:34 ` erik quanstrom
[not found] <<3e1162e60910150805q2ea3f682w688299a39274051c@mail.gmail.com>
2009-10-15 15:28 ` erik quanstrom
[not found] <<4AD70EE9.1010208@conducive.org>
2009-10-15 13:52 ` erik quanstrom
[not found] <<207092dc429fe476c2046d537aeaa400@hamnavoe.com>
2009-10-15 13:52 ` erik quanstrom
2009-10-15 15:07 ` David Leimbach
2009-10-15 15:21 ` roger peppe
2009-10-16 17:21 ` Sam Watkins
2009-10-16 23:39 ` Nick LaForge
2009-10-18 1:12 ` Roman Shaposhnik
2009-10-19 14:14 ` matt
2009-10-19 16:00 ` Sam Watkins
2009-10-14 19:09 Tim Newsham
2009-10-14 19:54 ` Roman Shaposhnik
2009-10-14 21:21 ` Tim Newsham
2009-10-14 21:33 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2009-10-14 21:42 ` Noah Evans
2009-10-14 21:45 ` erik quanstrom
2009-10-14 21:57 ` Noah Evans
2009-10-14 22:10 ` Eric Van Hensbergen
2009-10-14 22:21 ` Noah Evans
2009-10-15 1:03 ` David Leimbach
2009-10-15 1:50 ` Roman Shaposhnik
2009-10-15 2:12 ` Eric Van Hensbergen
2009-10-15 10:53 ` Sam Watkins
2009-10-15 11:50 ` Richard Miller
2009-10-15 12:00 ` W B Hacker
2009-10-16 17:03 ` Sam Watkins
2009-10-16 18:17 ` ron minnich
2009-10-16 18:39 ` Wes Kussmaul
2009-10-17 12:42 ` Roman Shaposhnik
2009-10-15 11:56 ` Josh Wood
2009-10-15 13:11 ` hiro
2009-10-15 15:05 ` David Leimbach
2009-10-18 1:15 ` Roman Shaposhnik
2009-10-18 3:15 ` Bakul Shah
[not found] ` <e763acc10910180606q1312ff7cw9a465d6af39c0fbe@mail.gmail.com>
2009-10-18 13:22 ` Roman Shaposhnik
2009-10-18 19:18 ` Bakul Shah
2009-10-18 20:12 ` ron minnich
2009-10-14 21:36 ` Eric Van Hensbergen
2009-10-15 2:05 ` Roman Shaposhnik
2009-10-15 2:17 ` Eric Van Hensbergen
2009-10-15 3:32 ` Tim Newsham
2009-10-15 3:59 ` Eric Van Hensbergen
2009-10-15 17:39 ` Tim Newsham
2009-10-15 18:28 ` Christopher Nielsen
2009-10-15 18:55 ` W B Hacker
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=4AE86533.3020706@maht0x0r.net \
--to=maht-9fans@maht0x0r.net \
--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).