From: Jeff Garzik <jeff@garzik.org>
To: Marc Perkel <marc@perkel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: SATA 150 vs SATA 300
Date: Thu, 24 Aug 2006 22:32:41 -0400 [thread overview]
Message-ID: <44EE6149.7000404@garzik.org> (raw)
In-Reply-To: <44EDBD0C.9040501@perkel.com>
Marc Perkel wrote:
> Another speed related question. How much faster are SATA II drives
> compared to regular SATA drives in real life? And - does NCQ really
> help? I'm just looking for a general guess in the form of, "The Disk IO
> upgrading to SATA II with NCQ will generally be X% faster." What value
> is X?
SATA 150 and SATA 300 refers to interface speed (1.5Gbps or 3Gbps).
Unless its entirely flash-based or RAM-based, it is highly unlikely that
your disk max out the SATA cable bandwidth.
There is "SATA II is x times faster" rule, because it depends on the
drive mechanics inside. A SATA II drive may be exactly the same speed
as SATA I, except that it is upgraded to support NCQ and other SATA II
features.
NCQ definitely helps.
Jeff
prev parent reply other threads:[~2006-08-25 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 14:51 SATA 150 vs SATA 300 Marc Perkel
2006-08-25 2:32 ` Jeff Garzik [this message]
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=44EE6149.7000404@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.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