linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: kernel 2.6.31.1 + Sil 3512 + WDC WD5000AAKS-00V1A0 = no NCQ and UDMA5 instead of UDMA6
Date: Thu, 17 Dec 2009 22:05:15 -0600	[thread overview]
Message-ID: <4B2AFF7B.4000007@gmail.com> (raw)
In-Reply-To: <4B2AFBDD.30601@hardwarefreak.com>

On 12/17/2009 09:49 PM, Stan Hoeppner wrote:
> Jeff Garzik put forth on 12/17/2009 9:10 PM:
>
>> Nope.  You are pretty much maxing out the drive, of whatever drive you
>> plug in.  The sata bus -- at its hardware spec'd maximum -- is far
>> faster than just about any drive, and the PCI bus is far faster than the
>> sata bus.
>
> I'm on the old 32bit/33MHz PCI bus of 133MB/s.  SATA1 at 150MB/s is
> slightly faster, no?  No argument here that both are far faster than
> almost all drives on the market.  I was just wondering if bumping up
> from the default UDMA/100 to UDMA/133 would allow quicker PCI bus
> bursting and thus a slight improvement in overall performance.

The UDMA speed doesn't make any difference at all with SATA, it's just 
an arbitrary number in almost all cases. Only the link speed really 
matters (which with these controllers will always be 1.5 Gbps).

>
>> You could probably max out the SATA bus with a RAM-based SATA device;
>> that's it.
>
> Yeah, I've seen some results published of quality SSDs and they just
> absolutely scream in latency, IOPs, and throughput.  That's not in my
> future, it's complete overkill for my applications, performance and
> dollar wise.  I just want to optimize the performance of what I already
> have.
>
> I think I only gave $15 for this Koutech Sil3512 PCI (32/33) controller
> at Newegg.  You being you with the knowledge you have, would buying one
> of the cards whose chipset supports NCQ, such as the sata_sil24 cards,
> be anything close to worth the additional investment in dollars and time
> spent swapping hardware and drivers?  Is NCQ the performance panacea
> that some purport it to be?  How much difference does it really make?

It's really hard to say, it depends on the drive and the workload, in 
most cases..

  reply	other threads:[~2009-12-18  4:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 14:16 kernel 2.6.31.1 + Sil 3512 + WDC WD5000AAKS-00V1A0 = no NCQ and UDMA5 instead of UDMA6 Stan Hoeppner
2009-12-17 18:01 ` Jeff Garzik
2009-12-18  2:22   ` Stan Hoeppner
2009-12-18  3:10     ` Jeff Garzik
2009-12-18  3:49       ` Stan Hoeppner
2009-12-18  4:05         ` Robert Hancock [this message]
2009-12-18  4:34           ` Stan Hoeppner
2009-12-18  5:00             ` Robert Hancock
2009-12-18 19:51               ` Stan Hoeppner
2009-12-19 18:16                 ` Robert Hancock
2009-12-19 23:15                   ` Stan Hoeppner
2009-12-19 23:29                     ` Jeff Garzik
2009-12-20  0:08                       ` Stan Hoeppner

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=4B2AFF7B.4000007@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=stan@hardwarefreak.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).