From: Nick Piggin <piggin@cyberone.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@digeo.com>,
Joel.Becker@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: WimMark I report for 2.5.65-mm2
Date: Fri, 21 Mar 2003 02:01:35 +1100 [thread overview]
Message-ID: <3E79D7CF.2020406@cyberone.com.au> (raw)
In-Reply-To: <20030320082947.GM4990@suse.de>
Jens Axboe wrote:
>On Thu, Mar 20 2003, Andrew Morton wrote:
>
>>Jens Axboe <axboe@suse.de> wrote:
>>
>>>Besides, deadline is still the most solid choice.
>>>
>>Deadline will always be the best choice for OLTP workloads. Or CFQ - it
>>should perform the same.
>>
>>All this workload does is seeks all over the disk doing teeny synchronous
>>I/O's. It is the worst-case for AS.
>>
>>What we are trying to do at present is to make AS not _too_ bad for these
>>workloads so that people with mixed workloads or who are not familiar with
>>kernel arcanery don't accidentally end up with something which is
>>significantly slower than it should be.
>>
>>It is an interesting test case.
>>
>
>I understand that. A deadline run is still interesting if there are
>regressions from -mm2 to -mm3, for example. If deadline shows the same
>regression, it's likely not a newly introduced AS bug.
>
You are quite right of course, Jens. I did tell Joel not to worry
about the other schedulers for a while just while I was trying to
get AS even close to their performance. I thought it would take a
bit longer to get there. It appears to be now, so yes, deadline
runs will be nice.
next prev parent reply other threads:[~2003-03-20 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 23:28 WimMark I report for 2.5.65-mm2 Joel Becker
2003-03-20 1:57 ` Andrew Morton
2003-03-20 0:38 ` Joel Becker
2003-03-20 0:55 ` Nick Piggin
2003-03-20 8:04 ` Jens Axboe
2003-03-20 8:20 ` Andrew Morton
2003-03-20 8:29 ` Jens Axboe
2003-03-20 15:01 ` Nick Piggin [this message]
2003-03-20 18:32 ` Joel Becker
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=3E79D7CF.2020406@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Joel.Becker@oracle.com \
--cc=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=linux-kernel@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