9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] "FAWN: Fast array of wimpy nodes" (was: Plan 9 - the next 20 years)
Date: Sun, 19 Apr 2009 12:52:47 -0400	[thread overview]
Message-ID: <6a38aded8b173af1fee172ca0403d745@quanstro.net> (raw)
In-Reply-To: <4f34febc0904190843u3337e22bn6472cbc26122fb7@mail.gmail.com>

> To clarify, I meant that given X vs. Y, the cost benefits of X
> eventually overwhelm the initial technical benefits of Y.
>
> With SATA vs. SCSI in particular, I wasn't so much thinking of command
> sets or physical connections but of providing cluster scale storage
> (i.e., 10's or 100's of TB) where it's fast enough and reliable enough
> but much cheaper to use commodity 7200 rpm SATA drives in RAID 5 than
> "server grade" 10k or 15k rpm SCSI or SAS drives.

this dated prejudice that scsi is for servers and ata is
for your dad's computer has just got to die.

could you explain how raid 5 relates to sata vs sas?
i can't see now it's anything but a non-sequitor.

you do realize that enterprise sata drives are available?
you do realize that many of said drives are built with the
same drive mechanism as sata hard drives?

as an example, the seagate es.2 drives are available with
a sas interface or a sata interface.

(by the way, enterprise drives are well worth it, as i discovered
on monday. :-(.)

while it's true there aren't any 15k sata drives currently
on the market, on the other hand if you want real performance,
you can beat sas by getting an intel ssd drive.  these are
not currently available in a sas.

- erik



  reply	other threads:[~2009-04-19 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  7:58 John Barham
2009-04-19 12:16 ` erik quanstrom
2009-04-19 15:43   ` John Barham
2009-04-19 16:52     ` erik quanstrom [this message]
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=6a38aded8b173af1fee172ca0403d745@quanstro.net \
    --to=quanstro@quanstro.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).