On 6 Aug 2002, Steven Cole wrote:
> That last one looks like the biggest cheat. Rather than optimizing for
> dbench, is there a set of pessimizing numbers which would optimally turn
> dbench into a semi-useful tool for measuring meaningful IO performance?
> Or is dbench really only useful for stress testing?
Yes, dbench is only useful as a stress testing tool.
A minor varation in kernel behaviour can change dbench
throughput by an order of magnitude and I'm not talking
about any specific kernel component here ... ANY kernel
component could trigger it.
While it is easy to measure dbench throughput, it is
nearly impossible to:
1) analyse why dbench throughput changed from kernel to kernel
2) predict the relation (if any) these changes in dbench
throughput have with changes in performance of real
applications, if any
3) identify which kernel subsystem was responsible for the
change in dbench performance
-- Bravely reimplemented by the knights who say "NIH".
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com 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 : Wed Aug 07 2002 - 22:00:31 EST