public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: markw@osdl.org
To: akpm@osdl.org
Cc: piggin@cyberone.com.au, linux-kernel@vger.kernel.org
Subject: Re: DBT-2 anticipatory scheduler and filesystem results with 2.6.1
Date: Wed, 21 Jan 2004 08:23:14 -0800 (PST)	[thread overview]
Message-ID: <200401211623.i0LGNHo04546@mail.osdl.org> (raw)
In-Reply-To: <20040119203845.332cd5df.akpm@osdl.org>

On 19 Jan, 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.

Ok, ran through a set of tests a -R of the
readahead-revert-lazy-readahead.patch.  Saw a significant improvement
with xfs, but the other file systems appeared to improve only marginally
compared to 2.6.1-mm4 with that patch.

Here's a summary compared to 2.6.1:

		% throughput change from 2.6.1 to 2.6.1-mm4 -R readahead
ext2		-4.9
ext3		-4.3
jfs		-5.1
reiserfs	-3.8
xfs		14.8

Here's the summary of the original 2.6.1-mm4 for reference:

		% throughput change from 2.6.1 to 2.6.1-mm4
ext2		-5.9%
ext3		-5.1%
jfs		-7.0%
reiserfs	-2.2%
xfs		-0.3%

And the link to the result details:
	http://developer.osdl.org/markw/fs/project_results.html

  parent reply	other threads:[~2004-01-21 16:23 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
2004-01-21 16:23   ` markw [this message]
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=200401211623.i0LGNHo04546@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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