public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: David Mansfield <david@cobite.com>
Cc: piggin@cyberone.com.au, lkml@dm.cobite.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59mm5 database 'benchmark' results
Date: Fri, 24 Jan 2003 15:03:40 -0800	[thread overview]
Message-ID: <20030124150340.32e57f19.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301241718440.32240-100000@admin>

David Mansfield <david@cobite.com> wrote:
>
> 
> Hi Nick, Andrew, lists,
> 
> I've been testing some recent kernels to see how they compare with a 
> particular database workload.  The workload is actually part of our 
> production process (last months run) but on a test server.  I'll describe 
> the platform and the workload, but first, the results :-)
> 
> kernel           minutes     comment
> -------------    ----------- ---------------------------------
> 2.4.20-aa1       134         i consider this 'baseline'
> 2.5.59           124         woo-hoo
> 2.4.18-19.7.xsmp 128         not bad for frankenstein's montster
> 2.5.59-mm5       157         uh-oh
> 
> Platform:
> HP LH3000 U3.  Dual 866 Mhz Intel Pentium III, 2GB ram.  megaraid 
> controller with two channels, each channel raid 5 PV on 6 15k scsi disks, 
> one megaraid LV per PV.
> 
> Two plain disks w/pairs of partitions in raid 1 for OS (redhat 7.3), a 
> second pair for Oracle redo-log (in a log 'group').
> 
> Oracle version 8.1.7 (no aio support in this release) is accessing
> datafiles on the two megaraid devices via /dev/raw stacked on top of
> device-mapper 

Rather impressed that you got all that to work ;)

It does appear that the IO scheduler change is not playing nicely with
software RAID.

> I'll test any kernel you throw my way.

Thanks.  Could you please try 2.5.59-mm5, with

http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.59/2.5.59-mm5/broken-out/anticipatory_io_scheduling-2_5_59-mm3.patch

reverted?



  reply	other threads:[~2003-01-24 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 16:48 2.5.59mm5, raid1 resync speed regression David Mansfield
2003-01-24 16:55 ` Nick Piggin
2003-01-24 18:18   ` David Mansfield
2003-01-24 18:41     ` Nick Piggin
2003-01-24 22:34       ` 2.5.59mm5 database 'benchmark' results David Mansfield
2003-01-24 23:03         ` Andrew Morton [this message]
2003-01-27 15:14           ` David Mansfield
2003-01-24 22:40     ` 2.5.59mm5, raid1 resync speed regression Mitchell Blank Jr

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=20030124150340.32e57f19.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=david@cobite.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dm.cobite.com \
    --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