If it is doing anything but the benchmark the results will be useless
but you probably already know that.
Assuming the machine is completely idle with no services currently
running (other than the one used to log in) then just try a bunch of
test cases for the usage pattern you expect to see (or want to use)
and interpret the numbers accordingly. Reducing the variables that
interact with what you are metering is the first step.
If you want a 'generic' (ie. not real usage) benchmark then try the
iogen port.
But with any benchmarks don't put a lot of trust in the numbers
especially if you only run one test set.
Run a bunch and pull out that old Stats 1 text and take the results
with a big huge grain of salt and realize you are not benchmarking
OpenBSD you are benching your hardware and configuration.
http://www.openbsd.org/cgi-bin/cvsweb/ports/sysutils/iogen/pkg/DESCR?
rev=1.2&content-type=text/x-cvsweb-markup
"iogen is an i/o generator. It forks child processes that each run a
mix of
reads and writes. The idea is to generate heavily fragmented files
to make the
hardware suffer as much as possible. This tool has been used to test
filesystems, drivers, firmware and hardware devices. It is by no
means meant
as a performance measuring tool since it tries to recreate the worst
case
scenario i/o."
You may already have considered all of the above but included in case
others on the list have not.
On 27-Jun-06, at 7:57 AM, Gabriel George POPA wrote:
Could someone tell me which is the most used disk-benchmarking
solution for OpenBSD 3.8?
I'm running a small production server and I don't want to disrupt
(too much) its activity. I would like
of course to perform non-destructive tests. I think there's
somethink wrong with my disk/os performance
but I don't know where to start. I think a benchmark utility will
be good (SMART neveals nothing).
He he he. I think all people are concerned about OpenBSD
performance these days...
--
Sean
