public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Now: Debian issues, WAS: XFS Filesystem not mounting
Date: Tue, 14 Sep 2010 22:51:51 -0500	[thread overview]
Message-ID: <4C9042D7.90001@hardwarefreak.com> (raw)
In-Reply-To: <29714426.post@talk.nabble.com>

pbrunnen put forth on 9/14/2010 8:07 PM:

> Always was intrigued by the SGI equipment in the labs when I was at
> University...  Never played with one though.  Checked out the specs of those
> Origin boxes you mention.  That was some horsepower for the time.

Some years ago NCSA was selling off some retired 128P O2K systems really
really cheap.  I was only about 4 hours away from Urbana Champaign at
the time and was really tempted.  I was planning on running _lots_ of
seti@home processes on it, mainly.  ;)

The price was really decent for what I'd be getting, but in the end I
just couldn't justify it, no matter how cool it would have been to have
a dual rack 32P SGI Origin 2000 running in the basement, crunching S@H.

The reality check was that I could build a new 4U quad Xeon box at the
time, of about the same overall performance, and with lots more disk,
for a mere fraction of the cost of the used O2K.  It wouldn't have the
cool SGI badge or run IRIX, but I wouldn't have to add 220v circuits in
the basement, or acquire a big 220v UPS, or pay a much larger monthly
electric bill.

A single socket 12-core 2 GHz Opteron 6100 series on a SuperMicro mobo
with quad DDR3 memory channels w/32 GB RAM, sitting on your desktop,
would simply run circles around that old 2 rack 32P O2K system, probably
5 to 1 or greater in parallel linpack--for less than $2k.

-- 
Stan



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-09-15  3:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 23:45 XFS Filesystem not mounting pbrunnen
2010-09-14  1:21 ` Dave Chinner
2010-09-14  4:29   ` pbrunnen
2010-09-14  5:40     ` Michael Monnerie
2010-09-14  6:25       ` Emmanuel Florac
2010-09-14 12:32         ` pbrunnen
2010-09-14 14:03           ` Michael Monnerie
2010-09-14 16:09             ` Stan Hoeppner
2010-09-14 16:35               ` pbrunnen
2010-09-14 18:03                 ` Now: Debian issues, WAS: " Stan Hoeppner
2010-09-14 20:32                   ` Emmanuel Florac
2010-09-15  1:07                     ` pbrunnen
2010-09-15  3:51                       ` Stan Hoeppner [this message]
2010-09-15 13:15                         ` pbrunnen
2010-09-15  0:44                   ` Dave Chinner
2010-09-15  2:54                     ` Stan Hoeppner
2010-09-15  0:49                   ` pbrunnen
2010-09-14 16:25             ` pbrunnen
2010-09-14  4:43   ` pbrunnen
2010-09-14  5:40     ` Dave Chinner

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=4C9042D7.90001@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /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