summaryrefslogtreecommitdiff
path: root/benchmarks/bonnie
diff options
context:
space:
mode:
authorjmmv <jmmv@pkgsrc.org>2003-05-06 17:40:18 +0000
committerjmmv <jmmv@pkgsrc.org>2003-05-06 17:40:18 +0000
commitf1446ddf2bf8118f432b3ac74c88db3d832669a8 (patch)
tree37ae7d212f46ef8018a7bd8c13edba7da1a47ed9 /benchmarks/bonnie
parent37170ce899bdf394cca1d0769b2215d84b15a7ee (diff)
downloadpkgsrc-f1446ddf2bf8118f432b3ac74c88db3d832669a8.tar.gz
Drop trailing whitespace. Ok'ed by wiz.
Diffstat (limited to 'benchmarks/bonnie')
-rw-r--r--benchmarks/bonnie/DESCR12
1 files changed, 6 insertions, 6 deletions
diff --git a/benchmarks/bonnie/DESCR b/benchmarks/bonnie/DESCR
index b93807f2ffc..a08bfc07576 100644
--- a/benchmarks/bonnie/DESCR
+++ b/benchmarks/bonnie/DESCR
@@ -3,15 +3,15 @@ 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
+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
+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.