From: David Mansfield <lkml@dm.cobite.com>
To: Andrew Morton <akpm@digeo.com>
Cc: piggin@cyberone.com.au, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.59mm5 database 'benchmark' results
Date: Mon, 27 Jan 2003 10:14:11 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301241749220.32240-100000@admin> (raw)
In-Reply-To: <20030124150340.32e57f19.akpm@digeo.com>
On Fri, 24 Jan 2003, Andrew Morton wrote:
> > 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
> >
> > 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 ;)
>
Me too. It's still got some rough edges, but 2.5.59 was the first version
that made it through because of this or that reason. I'm very impressed
personally.
>
> 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
Ok. The results are basically the same as 2.5.59 vanilla:
kernel minutes
----------------------------- ----------
2.5.59-mm5-no-anticipatory-io 125
Anything else?
David
--
/==============================\
| David Mansfield |
| lkml@dm.cobite.com |
\==============================/
next prev parent reply other threads:[~2003-01-27 15:05 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
2003-01-27 15:14 ` David Mansfield [this message]
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=Pine.LNX.4.44.0301241749220.32240-100000@admin \
--to=lkml@dm.cobite.com \
--cc=akpm@digeo.com \
--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
all inboxes | Powered by JetHome®