linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Default User <default_user@email.it>
To: Chris Worley <worleys@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Intel Updates SSDs, Supports TRIM, Faster Writes
Date: Wed, 11 Nov 2009 19:02:37 +0100	[thread overview]
Message-ID: <4AFAFC3D.3000402@email.it> (raw)
In-Reply-To: <f3177b9e0911100804y5f358194q422c9196ac14ec70@mail.gmail.com>

Chris Worley wrote:
> On Tue, Nov 10, 2009 at 8:48 AM, Asdo <asdo@shiftmail.org> wrote:
>   
>> I have not heard about these SSS you mention.
>> Do you have a link?
>>     
>
> All the Fusion-io products (fusionio.com) and TMS's (ramsan.com) RS20
> are two examples (not their RAM-based products).  Sun has their
> "Sunfire", but I haven't seen that yet.
>   
I don't know TMS, I know Fusion-io a bit: it is indeed 10x faster than a 
SSD but it is also 10 times more expensive!
If you make a raid-0 of ten SSDs in a good hardware-raid controller, 
exported to the OS as a single SCSI disk, I bet you obtain about the 
same performances.
Look at this:
http://www.tomshardware.com/reviews/x25-e-ssd-performance,2365.html
by looking at this page
http://www.tomshardware.com/reviews/x25-e-ssd-performance,2365-7.html
it seems the "streaming writes" is apparently similar to the benchmark 
you want (see the specs), do you agree? Yes it's 0% random it's 4 
workers... and the blocksize is the one you want.
You find the result in the following page. That's 2.2GB/sec with 16 
disks. If you imagine it with 8 disks and only 1 controller (the 
benchmark uses 2 controllers with a software raid-0 above) it's more 
than the speed you want (800MB/sec) and it's with a SCSI interface.

What do you think?

>> Also are you sure that the SATA/SCSI layer is the problem? Some hardware
>> raids can do 800 MB/s sequential, single stream, and indeed with a SATA/SAS
>> interface to the kernel. If what you say was true, that would be
>> impossible...
>>     
>
> Sequential/streaming performance is a corner case.  There are many
> high speed solutions to that (even using rotating media).  I'm talking
> random I/O at 128KB blocks at 800MB/s per drive.
>   


  reply	other threads:[~2009-11-11 18:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 17:57 Intel Updates SSDs, Supports TRIM, Faster Writes Bill Davidsen
2009-11-08 22:30 ` Thomas Fjellstrom
2009-11-09  1:13 ` Majed B.
2009-11-09 16:37   ` Chris Worley
2009-11-09 16:42     ` Majed B.
2009-11-09 16:59       ` Chris Worley
2009-11-10  9:42         ` Kasper Sandberg
2009-11-10 15:39           ` Chris Worley
2009-11-10 15:43             ` Majed B.
2009-11-10 15:58               ` Chris Worley
2009-11-10 16:01                 ` Majed B.
2009-11-10 16:15                   ` Robin Hill
2009-11-10 16:31                     ` Chris Worley
2009-11-10 16:18                   ` Chris Worley
2009-11-10 18:31                     ` Majed B.
2009-11-10 23:03                       ` Mathieu Chouquet-Stringer
2009-11-11  2:52                         ` Majed B.
2009-11-10 18:40                     ` Kasper Sandberg
2009-11-10 15:48             ` Asdo
2009-11-10 16:04               ` Chris Worley
2009-11-11 18:02                 ` Default User [this message]
2009-11-10 18:38             ` Kasper Sandberg
2009-11-10 16:36         ` Martin K. Petersen
2009-11-10 17:22           ` Chris Worley
2009-11-10 20:11             ` Martin K. Petersen
2009-11-10 20:45               ` Chris Worley
2009-11-10 22:35                 ` Martin K. Petersen
2009-11-11 18:17                   ` Chris Worley
2009-11-10 21:01               ` Greg Freemyer
2009-11-10 21:17                 ` Chris Worley
2009-11-10 22:56                 ` Martin K. Petersen
2009-11-11 17:00                   ` Greg Freemyer
2009-11-12  5:50                     ` Martin K. Petersen
2009-11-09 18:42   ` Greg Freemyer

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=4AFAFC3D.3000402@email.it \
    --to=default_user@email.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=worleys@gmail.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;
as well as URLs for NNTP newsgroup(s).