diff options
author | David E. O'Brien <obrien@FreeBSD.org> | 2002-08-27 15:55:42 +0000 |
---|---|---|
committer | David E. O'Brien <obrien@FreeBSD.org> | 2002-08-27 15:55:42 +0000 |
commit | 62252d236c78a1d49d595df95285fb1e1ed9e809 (patch) | |
tree | 508a771f7a83681b9a046e52070d8776efa16e6b /benchmarks | |
parent | b56f80f99ea91eacab5b5e685f011316722d3e20 (diff) | |
download | ports-62252d236c78a1d49d595df95285fb1e1ed9e809.tar.gz ports-62252d236c78a1d49d595df95285fb1e1ed9e809.zip |
It is easier to modify the manpage if it is a normal text rather than a patch.
Notes
Notes:
svn path=/head/; revision=65104
Diffstat (limited to 'benchmarks')
-rw-r--r-- | benchmarks/bonnie/Makefile | 2 | ||||
-rw-r--r-- | benchmarks/bonnie/files/bonnie.1 | 69 | ||||
-rw-r--r-- | benchmarks/bonnie/files/patch-aa | 73 |
3 files changed, 70 insertions, 74 deletions
diff --git a/benchmarks/bonnie/Makefile b/benchmarks/bonnie/Makefile index b7ac8b0d8425..2b6eb1afbd5b 100644 --- a/benchmarks/bonnie/Makefile +++ b/benchmarks/bonnie/Makefile @@ -21,6 +21,6 @@ MAKE_ARGS+= CFLAGS="${CFLAGS}" do-install: ${INSTALL_PROGRAM} ${WRKSRC}/Bonnie ${PREFIX}/bin/bonnie - ${INSTALL_DATA} ${WRKSRC}/bonnie.1 ${PREFIX}/man/man1 + ${INSTALL_MAN} ${FILESDIR}/bonnie.1 ${PREFIX}/man/man1 .include <bsd.port.mk> diff --git a/benchmarks/bonnie/files/bonnie.1 b/benchmarks/bonnie/files/bonnie.1 new file mode 100644 index 000000000000..c08073e1d2e0 --- /dev/null +++ b/benchmarks/bonnie/files/bonnie.1 @@ -0,0 +1,69 @@ +.\" $FreeBSD$ +.\" The following requests are required for all man pages. +.Dd May 18, 1995 +.Os UNIX +.Dt BONNIE 1 +.Sh NAME +.Nm bonnie +.Nd Performance Test of Filesystem I/O +.Sh SYNOPSIS +.Nm bonnie +.Op Fl d Ar scratch-dir +.Op Fl s Ar size-in-MB +.Op Fl m Ar machine-label + +.Sh DESCRIPTION +.Nm Bonnie +tests the speed of file I/O from standard C library calls. +It reads and writes 8KB blocks to find the maximum sustained +data rate (usually limited by the drive or controller) and additionally +rewrites the 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 test results depend 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 samples. +(See +.Sx BUGS +below.) + +.Sh OPTIONS +.Bl -tag -width indent +.It Fl d Ar scratch-dir +Specify the directory where the test file gets written. The default +is the current directory. Make sure there is sufficient free space +available on the partition this directory resides in. +.It Fl s Ar size-in-MB +Specify the size of the test file in MByte. This much space must be +available for the tests to complete. +.It Fl m Ar machine-label +Specify a label to be written in the first column of the result table. +.El + +.Sh SEE ALSO +.Xr iozone 1 , +.Xr iostat 8 + +.Sh AUTHOR +.Nm Bonnie +was written by Tim Bray <tbray@watsol.waterloo.edu>. + +.Sh BUGS +.Nm Bonnie +tries hard to measure disk performance and not the quality of the +buffer cache implementation. In merged buffer caches common today, +the buffer cache size is often only limited by total RAM on an otherwise +unloaded system. Be sure to use a file at least twice at large as +available RAM to protect against artificially high results. + +There is no way to keep the buffer cache from increasing the reported +seek rate. This is because the fraction of accesses corresponding to the +amount of the file cached, will be done without seeks. +If your buffer cache is half the size of the file used, then half the +requests will be satisfied immediately, and and the seek rate printed +will be twice the actual value. + diff --git a/benchmarks/bonnie/files/patch-aa b/benchmarks/bonnie/files/patch-aa deleted file mode 100644 index bf6c442a985a..000000000000 --- a/benchmarks/bonnie/files/patch-aa +++ /dev/null @@ -1,73 +0,0 @@ -*** /dev/null Thu May 18 20:25:21 1995 ---- bonnie.1 Thu May 18 20:26:47 1995 -*************** -*** 0 **** ---- 1,68 ---- -+ .\" The following requests are required for all man pages. -+ .Dd May 18, 1995 -+ .Os UNIX -+ .Dt BONNIE 1 -+ .Sh NAME -+ .Nm bonnie -+ .Nd Performance Test of Filesystem I/O -+ .Sh SYNOPSIS -+ .Nm bonnie -+ .Op Fl d Ar scratch-dir -+ .Op Fl s Ar size-in-MB -+ .Op Fl m Ar machine-label -+ -+ .Sh DESCRIPTION -+ .Nm Bonnie -+ tests the speed of file I/O from standard C library calls. -+ It reads and writes 8KB blocks to find the maximum sustained -+ data rate (usually limited by the drive or controller) and additionally -+ rewrites the 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 test results depend 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 samples. -+ (See -+ .Sx BUGS -+ below.) -+ -+ .Sh OPTIONS -+ .Bl -tag -width indent -+ .It Fl d Ar scratch-dir -+ Specify the directory where the test file gets written. The default -+ is the current directory. Make sure there is sufficient free space -+ available on the partition this directory resides in. -+ .It Fl s Ar size-in-MB -+ Specify the size of the test file in MByte. This much space must be -+ available for the tests to complete. -+ .It Fl m Ar machine-label -+ Specify a label to be written in the first column of the result table. -+ .El -+ -+ .Sh SEE ALSO -+ .Xr iozone 1 , -+ .Xr iostat 8 -+ -+ .Sh AUTHOR -+ .Nm Bonnie -+ was written by Tim Bray <tbray@watsol.waterloo.edu>. -+ -+ .Sh BUGS -+ .Nm Bonnie -+ tries hard to measure disk performance and not the quality of the -+ buffer cache implementation. In merged buffer caches common today, -+ the buffer cache size is often only limited by total RAM on an otherwise -+ unloaded system. Be sure to use a file at least twice at large as -+ available RAM to protect against artificially high results. -+ -+ There is no way to keep the buffer cache from increasing the reported -+ seek rate. This is because the fraction of accesses corresponding to the -+ amount of the file cached, will be done without seeks. -+ If your buffer cache is half the size of the file used, then half the -+ requests will be satisfied immediately, and and the seek rate printed -+ will be twice the actual value. -+ |