From: Steven Cole <elenstev@mesatop.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Jens Axboe <axboe@suse.de>, lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>, Steven Cole <scole@lanl.gov>
Subject: Re: Linux v2.4.19-rc5
Date: 06 Aug 2002 20:54:39 -0600 [thread overview]
Message-ID: <1028688882.2376.105.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.3.96.1020806205643.9199C-100000@gatekeeper.tmr.com>
On Tue, 2002-08-06 at 19:09, Bill Davidsen wrote:
> On Tue, 6 Aug 2002, Rik van Riel wrote:
>
> > On Mon, 5 Aug 2002, Bill Davidsen wrote:
> >
> > > > Here are some dbench numbers, from the "for what it's worth" department.
> > >
> > > Call me an optimist, but after all the reliability problems we had win the
> > > 2.5 series, I sort of hoped it would be better in performance, not
> > > increasingly worse. Am I misreading this? Can we fall back to the faster
> > > 2.4 code :-(
> >
> > Dbench is at its best when half (or more) of the dbench processes
> > are stuck semi-infinitely in __get_request_wait and the others can
> > operate in RAM without ever touching the disk.
> >
> > In effect, if you want the best dbench throughput you should make
> > the system completely unsuitable for real world applications ;)
>
> I assumed that the posted results were apples and apples. That may not be
Well, maybe Granny Smiths and Red Delicious. The problem with dbench is
that it checks how well they roll and bounce. But even that can be
important sometimes. ;)
> the case. If this was one kernel tuned for dbench and one for something
> else, then the information content is pretty low, to me at least. But if
> it is both tuned or both stock, then I would hope 2.5 would be better. If
> the text said that and I read past it, I apologise.
All kernels were stock as patched with no special changes to
/proc/sys/vm/bdflush for 2.4.x or to /proc/sys/vm/dirty* for 2.5.x.
Sorry, I didn't explicitly state that in the initial report.
Steven
next prev parent reply other threads:[~2002-08-07 3:15 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 6:38 Marcelo Tosatti
2002-08-01 7:49 ` Jens Axboe
2002-08-01 7:14 ` Marcelo Tosatti
2002-08-01 8:10 ` Jens Axboe
2002-08-01 9:02 ` Andrew Morton
2002-08-01 8:58 ` Jens Axboe
2002-08-01 14:45 ` Steven Cole
2002-08-01 18:57 ` Andrew Morton
2002-08-01 20:15 ` Steven Cole
2002-08-06 3:46 ` Bill Davidsen
2002-08-06 4:30 ` Andrew Morton
2002-08-06 14:07 ` Steven Cole
2002-08-06 14:20 ` Rik van Riel
2002-08-06 17:12 ` Andrew Morton
2002-08-06 5:42 ` Jens Axboe
2002-08-06 8:30 ` Adrian Bunk
2002-08-06 8:48 ` Jens Axboe
2002-08-06 10:31 ` Lincoln Dale
2002-08-06 12:59 ` Rik van Riel
2002-08-07 1:09 ` Bill Davidsen
2002-08-07 2:54 ` Steven Cole [this message]
2002-08-07 22:30 ` Bill Davidsen
2002-08-07 22:39 ` Rik van Riel
2002-08-07 23:44 ` Bill Davidsen
2002-08-07 23:53 ` Rik van Riel
2002-08-09 17:46 ` Bill Davidsen
2002-08-09 19:27 ` Rik van Riel
2002-08-01 7:55 ` Keith Owens
2002-08-01 8:10 ` Jens Axboe
2002-08-04 6:50 ` H. Peter Anvin
2002-08-01 11:32 ` Willy TARREAU
2002-08-01 13:54 ` Alan Cox
2002-08-01 12:48 ` Willy TARREAU
2002-08-01 12:12 ` Linux v2.4.19-rc5 - APM bug Willy TARREAU
2002-08-01 13:32 ` [PANIC] APM bug with -rc4 and -rc5 Willy TARREAU
2002-08-01 14:55 ` Alan Cox
2002-08-01 13:56 ` Willy Tarreau
2002-08-01 15:24 ` Willy Tarreau
2002-08-01 16:53 ` Alan Cox
2002-08-01 16:41 ` Willy Tarreau
2002-08-01 20:35 ` [PATCH] solved APM bug with -rc5 Willy TARREAU
2002-08-01 20:52 ` Richard Gooch
2002-08-01 20:54 ` Richard Gooch
2002-08-01 21:17 ` Willy TARREAU
2002-08-01 22:37 ` Alan Cox
2002-08-01 20:58 ` Dave Jones
2002-08-01 22:16 ` Alan Cox
2002-08-01 21:07 ` Willy Tarreau
2002-08-01 21:47 ` Linus Torvalds
2002-08-02 0:12 ` [PATCH] solved APM bug with -rc5 (take 2) Willy TARREAU
2002-08-02 1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02 2:29 ` Nick Orlov
2002-08-02 12:27 ` Alan Cox
2002-08-02 12:52 ` Nick Orlov
2002-08-02 14:00 ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45 ` Nick Orlov
2002-08-06 4:36 Linux v2.4.19-rc5 rwhron
2002-08-07 3:00 ` Bill Davidsen
2002-08-06 20:12 Peter Wong
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=1028688882.2376.105.camel@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=scole@lanl.gov \
/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®