public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: markw@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: DBT-2 anticipatory scheduler and filesystem results with 2.6.1
Date: Tue, 20 Jan 2004 15:55:56 +1100	[thread overview]
Message-ID: <400CB4DC.7090807@cyberone.com.au> (raw)
In-Reply-To: <20040119203845.332cd5df.akpm@osdl.org>



Andrew Morton wrote:

>markw@osdl.org wrote:
>
>> I ran some dbt-2 tests against 5 filesystems with 2.6.1-mm4 and 2.6.1. I
>> see a degradation from 0 to 7% in throughput. 
>>
>
>-mm4 also had readahead changes which will adversely impact database-style
>workloads.  I'd suggest that you revert
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/readahead-revert-lazy-readahead.patch
>
>and retest.
>
>We reverted lazy readahead because it broke NFS linear reads and was doing
>the wrong thing anyway.  We need to come up with something else for
>database-style workloads.
>
>

Oh good. I'd be a bit surprised if it were due to an as-iosched.c change 
that
caused the regression.

But there are changes in how new processes are handled, so if you have a lot
of io submitting processes being created, you might see a difference.



  reply	other threads:[~2004-01-20  4:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20  0:05 DBT-2 anticipatory scheduler and filesystem results with 2.6.1 markw
2004-01-20  4:38 ` Andrew Morton
2004-01-20  4:55   ` Nick Piggin [this message]
2004-01-21 16:23   ` markw
2004-01-22  7:00     ` 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=400CB4DC.7090807@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markw@osdl.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