public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.4.19-rc5
Date: Tue, 6 Aug 2002 00:36:48 -0400	[thread overview]
Message-ID: <20020806043648.GA23256@rushmore> (raw)

> I sort of hoped it would be better in performance, not
> increasingly worse.

There were a lot of improvements during the 2.4.19-pre series on 
several I/O benchmarks.  Comparing 2.4.18 to 2.4.19 on a quad xeon. 
Here are a few of the big changes (average of 5 runs):

200% improvement on reiserfs for dbench 192
125% improvement on ext3     for dbench 192
248% improvement on ext2     for dbench 192
 40% improvement on reiserfs for dbench  64
 30% improvement on ext3     for dbench  64
 67% improvement on ext2     for dbench  64
 30% improvement on ext2 for tiobench seq reads with threads >= 32
100% improvement on ext2 and reiserfs for tiobench seq writes with threads >= 32
300% drop in cpu usage on ext3 for tiobench seq reads
     (latency and throughput also improved)

In most cases, average and max tiobench latency went down with 2.4.19.
Max sequential write latency with one thread on ext2 went up 1000% though.

imho, it's worthwhile to track and investigate regressions
and improvements.

More benchmarks and several pre's and rc's in between at:
http://home.earthlink.net/~rwhron/kernel/bigbox.html

Small boxes are important too:
http://home.earthlink.net/~rwhron/kernel/k6-2-475.html
-- 
Randy Hron


             reply	other threads:[~2002-08-06  4:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06  4:36 rwhron [this message]
2002-08-07  3:00 ` Linux v2.4.19-rc5 Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06 20:12 Peter Wong
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
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

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=20020806043648.GA23256@rushmore \
    --to=rwhron@earthlink.net \
    --cc=linux-kernel@vger.kernel.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