public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: jens.axboe@oracle.com, LKML <linux-kernel@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>,
	mszeredi@suse.de
Subject: Re: Performance regression in IO scheduler still there
Date: Thu, 12 Nov 2009 15:44:02 -0500	[thread overview]
Message-ID: <x49pr7npj71.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20091112172941.GK14528@duck.suse.cz> (Jan Kara's message of "Thu, 12 Nov 2009 18:29:41 +0100")

Jan Kara <jack@suse.cz> writes:

> On Wed 11-11-09 12:43:30, Jeff Moyer wrote:
>> Jan Kara <jack@suse.cz> writes:
>> 
>> >   Sadly, I don't see the improvement you can see :(. The numbers are the
>> > same regardless low_latency set to 0:
>> > 2.6.32-rc5 low_latency = 0:
>> > 37.39 36.43 36.51 -> 36.776667 0.434920
>> >   But my testing environment is a plain SATA drive so that probably
>> > explains the difference...
>> 
>> I just retested (10 runs for each kernel) on a SATA disk with no NCQ
>> support and I could not see a difference.  I'll try to dig up a disk
>> that support NCQ.  Is that what you're using for testing?
>   I don't think I am. How do I find out?

Good question.  ;-)  I grep for NCQ in dmesg output and make sure it's
greater than 0/32.  There may be a better way, though.

>>               2.6.29    2.6.32-rc6,low_latency=0
>> ----------------------------------
>> Average:      34.6648   34.4475
>> Pop.Std.Dev.: 0.55523   0.21981
>   Hmm, strange. Miklos Szeredi tried tiobench on his machine and he also
> saw the regression. I'll try to think what could make the difference.

OK, I'll try again.

Cheers,
Jeff

  reply	other threads:[~2009-11-12 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 17:20 Performance regression in IO scheduler still there Jan Kara
2009-10-26 17:26 ` Jeff Moyer
2009-11-05 20:10 ` Jeff Moyer
2009-11-05 23:00   ` Corrado Zoccolo
2009-11-06 14:14     ` Jeff Moyer
2009-11-10 18:37       ` Jan Kara
2009-11-06 18:56   ` Jeff Moyer
2009-11-08 17:01     ` Corrado Zoccolo
2009-11-10 16:47       ` Jeff Moyer
2009-11-10 17:37         ` Corrado Zoccolo
2009-11-11 14:10   ` Jan Kara
2009-11-11 17:43     ` Jeff Moyer
2009-11-12 17:29       ` Jan Kara
2009-11-12 20:44         ` Jeff Moyer [this message]
2009-11-12 21:00           ` Jens Axboe
2009-11-12 21:05             ` Jeff Moyer
2009-11-13  7:45               ` Jens Axboe
2009-11-16 10:47           ` Jan Kara
2009-11-16 16:58             ` Jan Kara
2009-11-16 17:03               ` Jeff Moyer
2009-11-16 18:38                 ` Corrado Zoccolo
2009-11-16 22:17                 ` Jan Kara

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=x49pr7npj71.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=efault@gmx.de \
    --cc=jack@suse.cz \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@suse.de \
    /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