summaryrefslogtreecommitdiff
path: root/benchmarks/bonnie/DESCR
diff options
context:
space:
mode:
authorzuntum <zuntum>2001-10-31 22:52:58 +0000
committerzuntum <zuntum>2001-10-31 22:52:58 +0000
commitec263708b4436f2f6fe8ff2c5ddd38bc49dbd322 (patch)
treeb3c17888184b1b17ed1b1fa28f1697197bb0b4f6 /benchmarks/bonnie/DESCR
parent26e767802169bc1a013a3a64740d0a84afa59755 (diff)
downloadpkgsrc-ec263708b4436f2f6fe8ff2c5ddd38bc49dbd322.tar.gz
Move pkg/ files into package's toplevel directory
Diffstat (limited to 'benchmarks/bonnie/DESCR')
-rw-r--r--benchmarks/bonnie/DESCR17
1 files changed, 17 insertions, 0 deletions
diff --git a/benchmarks/bonnie/DESCR b/benchmarks/bonnie/DESCR
new file mode 100644
index 00000000000..b93807f2ffc
--- /dev/null
+++ b/benchmarks/bonnie/DESCR
@@ -0,0 +1,17 @@
+Bonnie: Filesystem Benchmark Program
+
+Bonnie tests the speed of file I/O using standard C library calls.
+It does reads and writes of blocks, testing for the limit of sustained
+data rate (usually limited by the drive or controller) and updates on
+a file (better simulating normal operating conditions and quite dependent
+on drive and OS optimisations).
+The per character read and write tests are generally limited by CPU speed
+only on current generation hardware. It takes some 35 SPECint92 to read
+or write a file at a rate of 1MB/s using getc() and putc().
+The seek tests are dependent on the buffer cache size, since the fraction
+of disk blocks that fits into the buffer cache will be found without any
+disk operation and will contribute zero seek time readings. I.e. if the
+buffer cache is 16MB and the Bonnie test file is 32MB in size, then the
+seek time will come out as half its real value. The seek time includes
+rotational delay, and will thus always come out higher than specified for
+a drive.