linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@seoss.co.uk>
To: linux-ide@vger.kernel.org
Subject: Western Digital Velociraptor WD740ADFD-00NLR5 - NCQ performance falls off a cliff wi queue depth greater than two
Date: Mon, 12 Oct 2009 15:18:48 +0100	[thread overview]
Message-ID: <4AD33AC8.6000505@seoss.co.uk> (raw)

Hello,

I have what looks like a firmware or design performance bug with some 
74G WD Velociraptors WD740ADFD-00NLR5 (firmware 21.07QR5).  Sequential 
read speed (as measured with 'hdparm -t') drops-off with NCQ depths 
greater than 2.

Queue-depth(cmds) Speed(MB/s)

1   84
2   84
3   46
5   39
10   39
20   44
31   36

The speed given is the best of 10 - the system was under light load (I 
couldn't completely unload it, unfortunately).

Western Digital helpfully suggested that I contact my Linux vendor...


The system is a Tyan server with a Core2Quad Q6600  @ 2.40GHz, and an 
ICH9 running Debian 5.0 - kernel 2.6.26-2-openvz-amd64, SATA ports in 
non-RAID/AHCI/native mode.

I measured the speed like this:

for i in {1..31} ; do echo $i > /sys/block/sda/device/queue_depth ; echo 
-n "$( cat /sys/block/sda/device/queue_depth | head -c -1 )," ; for j in 
{1..10} ; do (hdparm -t /dev/sda | egrep -o 
'[[:digit:]]+\.[[:digit:]]+[[:space:]]+MB/sec' | head -c -1 ) ; done ; 
echo ; done | sed 's/ MB\/sec/,/g'

... and created a chart and max speed data in openoffice:

http://buttersideup.com/files/wd-raptor-NCQ-bug-1.pdf

with a second run here:

http://buttersideup.com/files/wd-raptor-NCQ-bug-2.pdf

Any comments or suggestions welcome - I'd be happy to repeat the test 
using a different benchmark if anyone can suggest a command-line they'd 
like run?

Cheers,

Tim.

-- 
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.  
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53  http://seoss.co.uk/ +44-(0)1273-808309


                 reply	other threads:[~2009-10-12 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AD33AC8.6000505@seoss.co.uk \
    --to=tim@seoss.co.uk \
    --cc=linux-ide@vger.kernel.org \
    /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).