Re: [BENCHMARK] ext3, reiser, jfs, xfs effect on contest

From: Con Kolivas (conman@kolivas.net)
Date: Fri Jan 31 2003 - 09:18:48 EST


On Saturday 01 Feb 2003 1:09 am, Mike A. Harris wrote:
> On Sat, 1 Feb 2003, Con Kolivas wrote:
> >Using the osdl hardware (http://www.osdl.org) with contest
> >(http://contest.kolivas.net) I've conducted a set of benchmarks with
> >different filesystems. Note that contest does not claim to be a throughput
> >benchmark.
> >
> >All of these use kernel 2.5.59
> >
> >First a set of contest benchmarks with the io load on a different hard
> > disk containing each of the four filesystems:
> >
> >io_other:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2559ext3 3 89 84.3 2 5.5 1.13
> >2559reiser 3 87 86.2 2 5.7 1.10
> >2559jfs 3 87 86.2 3 5.7 1.10
> >2559xfs 3 87 86.2 2 4.5 1.10
> >
> >I found it interesting that there is virtually no difference in kernel
> >compilation time with all fs. However jfs consistently wrote more during
> > the io load than the other fs.
> >
> >
> >This is a set of benchmarks with the kernel compilation and load all
> > performed on each of the fs:
>
> Compilation is inherently CPU bound, not disk I/O bound, so
> compiling the kernel (or anything for that matter) isn't going to
> show any difference really because the CPU Mhz and L1/L2 cache
> are the bottleneck.

When the io load is on another hard disk yes, however the results do show
differences when the load is on the same hard disk - these are two different
tests. There is more to kernel compilation than just cpu usage.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jan 31 2003 - 22:00:25 EST