[MMTests] Sysbench read-only on ext3

From: Mel Gorman
Date: Mon Jul 23 2012 - 17:13:37 EST

Configuration: global-dhp__io-sysbench-large-ro-ext3
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext3
Benchmarks: sysbench


Very large number of regressions.

Benchmark notes

mkfs was run on system startup. No attempt was made to age it. No
special mkfs or mount options were used.

sysbench is an OLTP-like benchmark. The test type was "complex" and
read-only. The table size was 50,000,000 rows regardless of memory size
but far exceeds the memory size of any of the test machines. sysbench
was chosen because it's a reasonably complex OLTP-like benchmark with
straight-forward prerequisites.

The backing database was postgres.

Machine: arnold
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext3/arnold/comparison.html
Arch: x86
CPUs: 1 socket, 2 threads
Model: Pentium 4
Disk: Single Rotary Disk

Oddly two clients is better but 1 or 4 is worse.

Swapping for kernels 3.1 and 3.2 is crazy. Direct reclaim started since
2.6.39 and has not eased off but in the context of the overall test is
very low.

Machine: hydra
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext3/hydra/comparison.html
Arch: x86-64
CPUs: 1 socket, 4 threads
Model: AMD Phenom II X4 940
Disk: Single Rotary Disk
Status: Ok

There are a lot of regressions here that were mostly introduced between
2.6.39 and 3.0. In general, this is looking bad.

Swapping in kernel 3.1 was higher.

Machine: sandy
Result: http://www.csn.ul.ie/~mel/postings/mmtests-20120424/global-dhp__io-sysbench-large-ro-ext3/sandy/comparison.html
Arch: x86-64
CPUs: 1 socket, 8 threads
Model: Intel Core i7-2600
Disk: Single Rotary Disk

Generally this is telling a much better story but this could be because
of the much larger memory size of this machine offsetting some other

Swapping in 3.1 and 3.2.

Mel Gorman
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/