If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Yes, but I/O scheduler will be probably set for throughput for final 2.6.32. Afaik it's set for low latency in -rc and some benchmarks suffer from this. It should be optimized and set default for 2.6.33.
I/O scheduler is set for low latency in the final 2.6.32 and this can have impact on some benchmarks. From kernel newbies:
In this release, the CFQ IO scheduler (the one used by default) gets a new feature that greatly helps to reduce the impact that a writer can have on the system interactiveness. The end result is that the desktop experience should be less impacted by background IO activity, but it can cause noticeable performance issues, so people who only cares about throughput (ie, servers) can try to turn it off echoing 0 to /sys/class/block/<device name>/queue/iosched/low_latency. It's worth mentioning that the 'low_latency' setting defaults to on.
Starting by looking at the CPU usage during the playback of a 1080p H.264 video file, the Linux 2.6.32 kernel had the lowest overall CPU usage when using X-Video with MPlayer. However, the CPU usage was only less by 2%.
Looks like there is an error! The graph says
2.6.30 = 32.3
2.6.31 = 37.2
2.6.32 = 39.1