9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Barham <jbarham@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] "FAWN: Fast array of wimpy nodes" (was: Plan 9 - the next 20 years)
Date: Sun, 19 Apr 2009 00:58:43 -0700	[thread overview]
Message-ID: <4f34febc0904190058u1507f60fldc51ab3eab1f09fe@mail.gmail.com> (raw)

I certainly can't think ahead 20 years but I think it's safe to say
that the next 5 (at least doing HPC and large-scale web type stuff)
will increasingly look like this:
http://www.technologyreview.com/computing/22504/?a=f, which talks
about building a cluster from AMD Geode (!) nodes w/ compact flash
storage.  Sure it's not super-fast, but it's very efficient per watt.
If you had more cash you might substitute HE Opterons and SSD's but
the principle is the same.

The general trend is that capital expenditures for computing are going
down but operating expenditures are going up.  Indeed if you sign up
for something like Amazon's EC2 service, your initial capital outlay
is exactly $0.  (I vividly recall paying over $3000 for a low-end
server and $300/month in colo fees back in early 2003 when I had a
hosting business.)

Apparently they use the above cluster to implement some type of
distributed memcached style cache.  Here is the page listing the many
clients for memcached:
http://code.google.com/p/memcached/wiki/Clients.  However, if w/ Plan
9 you implement the interface to the cache as a 9p service, it is
automatically available to any language that can do file I/O (heck,
even Haskell, if you can slog through the advanced type theory).  So
your software development costs go down.

Another change that levels the playing field in Plan 9's favor is the
clock-speed wall and the move to multi-core chips.  Soon everyone is
going to have to re-write their software to make it concurrent if they
want to make it run faster.  And concurrency is hard, especially when
the predominant model is preemptive threads.  Here again Plan 9's
technical advantages of its lightweight kernel and CSP threading model
confers an economic advantage.

I think the key to successfully being able to use Plan 9 commercially
is to use its unique technical advantages to exploit disruptive
economic changes.  Economics beats technology every time (e.g.,
x86/amd64 vs. MIPS/Itanium, Ethernet vs. Infiniband, SATA vs. SCSI) so
don't try to fight it.

  John



             reply	other threads:[~2009-04-19  7:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  7:58 John Barham [this message]
2009-04-19 12:16 ` erik quanstrom
2009-04-19 15:43   ` John Barham
2009-04-19 16:52     ` erik quanstrom
2009-04-20 15:11       ` John Barham
2009-04-20 16:48         ` erik quanstrom
2009-04-19 14:27 ` Eric Van Hensbergen
2009-04-19 20:11   ` tlaronde
2009-04-20 15:48 ` ron minnich
2009-04-20 17:15   ` Wes Kussmaul

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=4f34febc0904190058u1507f60fldc51ab3eab1f09fe@mail.gmail.com \
    --to=jbarham@gmail.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).