public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Mike Sullivan <mksully@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: I/O degredation with AS on 2.6.0-test3
Date: Thu, 18 Sep 2003 08:57:22 +1000	[thread overview]
Message-ID: <3F68E6D2.50204@cyberone.com.au> (raw)
In-Reply-To: <OF7EFA21A7.C5FDCD40-ON85256DA4.005356E3@us.ibm.com>



Mike Sullivan wrote:

>
>>>Dave Hansen wrote:
>>>
>>>You might want to try Martin Bligh's diffprofile utility.  It's a bit
>>>hard to compare 2 500-line profiles without it.
>>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/tools/
>>>
>>>Also, there have evidently been a few I/O scheduler fixes since -test3.
>>>Please retry with -test5.
>>>
>>>
>
>>Nick Piggen wrote:
>>More important, are they regressions vs. previous kernels with AS?
>>
>
>I've checked 2.5.69mm9, 2.5.75, 2.6.0test3, and 2.6.0test5 and they all
>show a
>significant degradation in IO performance (>40%) when using the as
>scheduler
>compared to the deadline scheduler.
>
>Configuration: IBM x440 8way with hypertheading enabled, 16GB RAM,
>4 QLA2310 FC adapters attached to 2 FastT900 controllers
>(112 disks total). The 112 physical disks are striped as 8 raid 0
>logical disks. There are a total of 40 raw devices setup (5 per raid0
>disk).
>
>I've reattached excerpts from the database test for vmstat and
>the readprofile diffs created from Martin's diffprofile utility
>(diffprofile readp.as readp.dl).
>

Thanks Mike, I'll get a patch for you to try soon. I'm a bit busy ATM.



  reply	other threads:[~2003-09-17 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 15:22 I/O degredation with AS on 2.6.0-test3 Mike Sullivan
2003-09-17 22:57 ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-08 18:58 Mike Sullivan
2003-09-08 20:26 ` I/O degredation with AS on 2.6.0-test3 Dave Hansen
2003-09-09  2:44   ` Nick Piggin

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=3F68E6D2.50204@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mksully@us.ibm.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