[lkml]   [2001]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.2 vs. 2.4 benchmarks
Chris Evans wrote:
> Hi,
> I ran some 2.2 vs. 2.4 benchmarks, particularly in the area of file i/o,
> using bonnie++.
> The machine is a SMP 128Mb PII-350 with a udma2 drive capable of some
> 20Mb/sec+. Kernels involved are 2.4.0, and the default RH7.0 kernel
> (2.2.16 plus more patches than you can shake a stick at).
> Not going too much into the gory details, here are the differences exposed
> between 2,2 and 2.4:
> 1) Amazing 2.4 increase in streaming write performance; 13Mb/sec ->
> 20Mb/sec. I suspect this is the result of the "last minute" 2.4.0 dirty
> buffer/sync waiting handling changes.
> 2) Slight 2.4 increase in streaming read performance; 16Mb/sec ->
> 17Mb/sec. This leaves 2.4.0 writing faster than reading, I find that
> surprising.
I am not surprised. Reading _have_
to read the stuff before presenting a result. So you are completely
bound by
IO waiting, unless the stuff is cached. But test-programs tend to
empty the cache first. Writes can be buffered partially even if the
testfile is
much larger than memory. The extra 3Mb/s might be going into RAM.
128M with 3M/s takes about 43s. 20M/s in 43s is about 850M. Did you
use a
testfile in the 500MB-1000MB range?

> 3) Some 10% drop in rewrite performance from 2.2 -> 2.4 (possibly because
> page aging, like LRU, isn't too hot for the 2nd+ linear scan over data)
> 4) File creation 30% faster in 2.4; random deletes 30% faster; sequential
> deletes 10% slower.
> I did one other quick test, with disappointing results for 2.4.0. I did a
> kernel build with 32Mb.
> 2.4.0 was taking about 10 mins to do the build. 2.2.x was 1min30 quicker
> :( I was hoping/expecting the 2.4.0 page aging to do better, due to
> keeping the more useful pages in RAM better. I have no explanation.

You built exactly the same kernel in each case? (Version and options)
With the same amount of other software (X, daemons,...) running?
Using the same source tree? (Different disk locations may have large
differences) The circumstances where the same? (Doing a make
in order to get rid of files from the previous build will cache the
directory contents and be unfair if it happened in only one of the

Helge Hafting
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.073 / U:0.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site