non-representative DB benchmark

[Bob Friesenhahn]

Matthias,

Many of your benchmark runs are too short to be statistically
accurate.  Remember that the scheduler runs on a 100HZ clock and this
is used to account for user & system times.  Unless the system
provides dedicated hardware for a high-resolution clock (and this is
used by the 'time' command) the elapsed time measurements are suspect
as well.  I don't believe normal PC hardware provides a good
high-resolution clock.  Timings made on a Sun workstation using
'ptime', or another hardware/OS with access to precision timing would
be preferable.

Due to these reasons, it is best to find benchmarks which execute for
at least ten seconds.

The page-in/page-out values when using the various databases are most
interesting.  It would be interesting to see how the paging effects
short runs vs long runs.

Bob
======================================
Bob Friesenhahn
bfriesen at simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen