From: Matthew Wilcox <matthew@wil.cx>
To: Raz Ben-Yehuda <razb@bitband.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Intel X25-M MLC SSD benchmarks
Date: Wed, 10 Dec 2008 20:44:24 -0700 [thread overview]
Message-ID: <20081211034423.GA26095@parisc-linux.org> (raw)
In-Reply-To: <83CA05F64804AF43B8F733C4ABDFAA51022D04D7@mail1.bitband.com>
On Thu, Dec 11, 2008 at 12:12:37AM +0200, Raz Ben-Yehuda wrote:
> I did not want to dive into details because it does not matter. Whether
> noop,deadline, deadline parameters...
> As for the controller I used 4 different controllers. Adaptec,AHCI and
> Intel as Integrated chips on the 1025W-UR supermicro motherboard, and a
> 4-th controller SuperMicro UIO Adaptec aac card.
> All gave same results for most dd writes commands.
> dd if=/dev/zero of=/dev/sda bs=1M count=1000 oflag=direct , and many
> other variants such erase block size ( 128K ) , several erase block size
> and so on. Kernel is 2.6.18-8.el5.
OK, I suspect you aren't giving the drive enough work to do for it to
perform at its best. Try doing something like this:
for i in $(seq 0 9); do \
dd if=/dev/zero of=/dev/sda bs=1M count=1000 oflag=direct \
seek=$(($i * 1000)) & \
done
> I used all on a supermicro 1025W-UR. Disks have a SAS interface, 80GB.
> Also, I would like to note, I have 8 disks in array, while each one
> perform READS 250 MB/s, together I degrade to 200 MB/s each. As for
That doesn't surprise me; you're probably hitting a limitation either of
the array or the cable itself. A SAS cable can run up to 6Gbps, which
will be around 600MB/s. So three drives should be able to saturate your
SAS cable. If you're using an x4 link, that goes up to 2400MB/s which
should be ample for 8 drives ... maybe you're using a 3Gbps cable which
would limit each drive to 150MB/s.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-12-11 3:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AclbDGOLOskD7sbdTh+kIygApfPXZg==>
2008-12-10 21:15 ` Intel X25-M MLC SSD benchmarks Raz Ben-Yehuda
2008-12-10 21:39 ` Matthew Wilcox
2008-12-10 22:12 ` Raz Ben-Yehuda
2008-12-11 3:44 ` Matthew Wilcox [this message]
2008-12-12 3:27 ` Eric D. Mudama
2008-12-12 4:55 ` Eric D. Mudama
2008-12-12 7:15 ` Bart Van Assche
2008-12-12 14:25 ` Eric D. Mudama
2008-12-12 15:20 ` Matthew Wilcox
2008-12-12 15:55 ` Eric D. Mudama
2008-12-12 17:12 ` Raz Ben-Yehuda
2008-12-12 12:15 ` Matthew Wilcox
2008-12-12 12:21 ` Raz Ben-Yehuda
2008-12-12 18:10 ` 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=20081211034423.GA26095@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=razb@bitband.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).