The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: "Steve Simon" <steve@quintile.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Faster cpus at any cost
Date: Fri, 29 Jun 2018 14:13:04 -0400	[thread overview]
Message-ID: <20180629141304.4f10ed7f@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <a1117f6b1a451ac858ba5cd8c1e84280@quintile.net>

On Fri, 29 Jun 2018 09:51:55 +0100 "Steve Simon" <steve@quintile.net>
wrote:
> I know this is a dangerous game to play, but what of the future?
> 
> I am intrigued by the idea of true optical computers,
> perhaps the $10M super-computer will return?

One problem with optical is feature size. Even ultraviolet 200nm light
waves are pretty big compared to the feature size we now have in the
best chips (which is under 10nm at this point, though it will soon
stall out.) If you want EM waves that are close to the size of
current features, you're in the range of X-rays and aren't going to
have an easy time manipulating them.

All that said, a different kind of gedankenexperiment:

Say you wanted to store data as densely as possible. Lets ignore how
you would manage to read it and consider things on the same order of
magnitude of "as dense as we're going to get". If you stored 1s and
0s as C12 and C13 atoms in a diamond lattice, you get about
1.75e23 bits per cc, or about 12 zettabytes per cc. (Someone should
check my math.) I think it might be hard to do more than an order of
magnitude better than that. So, that's a crazy amount of storage, but
it looks like a pretty strong limit.

> GPUs have definitely taken over in some areas - even where
> SIMD would not seem a good fit. My previous employer does motion
> estimation of realtime video and has moved from custom electronics
> and FPGAs to using off the shelf GPUs in PCs.

Not surprised to hear. They're kind of everywhere at this point,
especially in scientific computation.

Perry
-- 
Perry E. Metzger		perry@piermont.com

      parent reply	other threads:[~2018-06-29 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1530237601.20140.tuhs@minnie.tuhs.org>
2018-06-29  8:51 ` Steve Simon
2018-06-29 17:14   ` Bakul Shah
2018-06-29 18:12   ` Toby Thain
2018-06-29 18:13   ` Perry E. Metzger [this message]

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=20180629141304.4f10ed7f@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=steve@quintile.net \
    --cc=tuhs@minnie.tuhs.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 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).