From: Tejun Heo <htejun@gmail.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: A question about NCQ
Date: Tue, 16 May 2006 19:49:05 +0900 [thread overview]
Message-ID: <4469AE21.6000304@gmail.com> (raw)
In-Reply-To: <1147773689.7273.88.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> Hi, Tejun
>
> Since your NCQ patches were pushed into #upstream, I decide to compare
> the performance between with and without NCQ enabling.
>
> But initial test result of running iozone with O_DIRECT option turned on
> didn't show the visible performance gain with NCQ. In certain cases, NCQ
> even had a worse performance than without NCQ.
>
> So my question is in what usage case can we observe the performance gain
> with NCQ?
>
I don't know the workload of iozone. But NCQ shines when there are many
concurrent IOs in progress. A good real world example would be busy
file-serving web server. It generally helps if there are multiple IO
requests. If iozone is single-threaded (IO-wise), try to run multiple
copies of them and compare the results.
Also, you need to pay attention to IO schedule in use, IIRC as and cfq
are heavily optimized for single-queued devices and might not show the
best performance depending on workload. For functionality test, I
usually use deadline. It's simpler and usually doesn't get in the way,
which, BTW, may or may not translate into better performance.
--
tejun
next prev parent reply other threads:[~2006-05-16 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 10:01 A question about NCQ zhao, forrest
2006-05-16 10:49 ` Tejun Heo [this message]
2006-05-17 2:21 ` zhao, forrest
2006-05-17 2:37 ` Tejun Heo
2006-05-17 3:24 ` zhao, forrest
2006-05-17 3:54 ` Tejun Heo
2006-05-17 4:04 ` Nick Piggin
2006-05-17 3:19 ` Jeff Garzik
2006-05-17 3:50 ` zhao, forrest
2006-05-17 14:31 ` Mark Lord
2006-05-18 1:56 ` Tejun Heo
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=4469AE21.6000304@gmail.com \
--to=htejun@gmail.com \
--cc=forrest.zhao@intel.com \
--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).