News for hackers. Stuff that matters.
Re:Five Years Of Linux Kernel Benchmarks: 2.6.12 Through 2.6.37 by dododo on Wednesday November 03, 2010 @03:05PM (#1866025)
the choice of some of these benchmarks is weird. they have a bunch of cpu-bound benchmarks. why exactly would you expect these to change as the kernel changed? (i would expect changing compiler to have a bigger influence.)

the ones that do change (and improve mostly) are ones where the kernel actually plays a role--file system, network, etc.

the iozone benchmark is a bit surprising, it shows no improvement. but they are hitting 200MB/s, so i wonder if this is simply because linux is hitting the max speed of the disk.

all in all, not very useful.

Re:Five Years Of Linux Kernel Benchmarks: 2.6.12 Through 2.6.37 by wmf on Wednesday November 03, 2010 @03:46PM (#1866196)
In general Moronix doesn't know what they're doing, but such benchmarks can be useful as regression tests; if the kernel isn't giving you full hardware performance then you have a problem.
Re:Five Years Of Linux Kernel Benchmarks: 2.6.12 Through 2.6.37 by bconway on Wednesday November 03, 2010 @03:32PM (#1866137)
the choice of some of these benchmarks is weird. they have a bunch of cpu-bound benchmarks. why exactly would you expect these to change as the kernel changed?

Scheduling is a non-trivial task, and the kernel scheduler underwent significant work during 2.4 and early 2.6. I think the reason those graphs are so boring is because the tests involve single process/single thread benchmarking.