Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tiotest(1) [debian man page]

tiotest(1)																tiotest(1)

NAME
tiotest - Threaded I/O bench SYNOPSIS
tiotest [-h] [-W] [-f SizeInMB] [-d TestDir] [-b BlkSizeInBytes] [-r NumberRandOpsPerThread] [-t NumberOfThreads] [-T] [-c] [-L] [-S] [-R] [-D DebugLevel] [-k SkipTestNoN] DESCRIPTION
tiotest is a file system benchmark especially designed to test I/O performance with multiple running threads. OPTIONS
-h Display a brief help and exit. -W Instructs tiotest to wait for previous thread to finish before starting a new one in the writing phase. This results in the files to be sequentially allocated and thus prevents them to be fragmented. Of course the writeside test is not parallel then but in readside the files are physically more sequentially placed on the media (well this depends on the filesystem too). -f SizeInMB The filesize per threat in MBytes. Defaults to 10 MB. -d TestDir The directory in which to test. Defaults to ., the current directory. -b BlkSizeInBytes The blocksize in Bytes to use. Defaults to 4096. -r NumberRandOpsPerThread Random I/O operations per thread. Defaults to 1000. -t NumberOfThreads The number of concurrent test threads. Defaults to 4. -T More terse output. -c Consistency check data. This should be used for stresstesting the media rather than benchmarking (it will slow io and raise cpu percentage). It is especially usefull to seek media for very hard to detect errors. -L Hide latency output. -S Do writing synchronously. -R Use raw drives. -D DebugLevel Set the debug level. -k fISkipTestNoN Skip test number n. Could be used several times. Example: while tiotest -c -f 2000 ; do echo run ok ; done To get usefull results the used file sizes should be a lot larger than the physical amount of memory you have. A good idea is to boot with 16 Megs of RAM (Try passing the "mem=16M" option to the kernel to limit Linux to using a very small amount of memory) and into Single User mode only. SEE ALSO
tiobench(1), bonnie(1), hdparm(8) AUTHOR
tiotest was written by Mika Kuoppala <miku@iki.fi>. This manual page was written by Peter Palfrader <weasel@debian.org>, for the Debian GNU/Linux system (but may be used by others). Mac-2001 tiotest(1)

Check Out this Related Man Page

GO-TESTFLAG(7)						 Miscellaneous Information Manual					    GO-TESTFLAG(7)

NAME
go - tool for managing Go source code DESCRIPTION
The 'go test' command takes both flags that apply to 'go test' itself and flags that apply to the resulting test binary. The test binary, called pkg.test, where pkg is the name of the directory containing the package sources, has its own flags: -test.v Verbose output: log all tests as they are run. -test.run pattern Run only those tests and examples matching the regular expression. -test.bench pattern Run benchmarks matching the regular expression. By default, no benchmarks run. -test.cpuprofile cpu.out Write a CPU profile to the specified file before exiting. -test.memprofile mem.out Write a memory profile to the specified file when all tests are complete. -test.memprofilerate n Enable more precise (and expensive) memory profiles by setting runtime.MemProfileRate. See 'godoc runtime MemProfileRate'. To pro- file all memory allocations, use -test.memprofilerate=1 and set the environment variable GOGC=off to disable the garbage collector, provided the test can run in the available memory without garbage collection. -test.parallel n Allow parallel execution of test functions that call t.Parallel. The value of this flag is the maximum number of tests to run simultaneously; by default, it is set to the value of GOMAXPROCS. -test.short Tell long-running tests to shorten their run time. It is off by default but set during all.bash so that installing the Go tree can run a sanity check but not spend time running exhaustive tests. -test.timeout t If a test runs longer than t, panic. -test.benchtime n Run enough iterations of each benchmark to take n seconds. The default is 1 second. -test.cpu 1,2,4 Specify a list of GOMAXPROCS values for which the tests or benchmarks should be executed. The default is the current value of GOMAXPROCS. For convenience, each of these -test.X flags of the test binary is also available as the flag -X in 'go test' itself. Flags not listed here are passed through unaltered. For instance, the command go test -x -v -cpuprofile=prof.out -dir=testdata -update will compile the test binary and then run it as pkg.test -test.v -test.cpuprofile=prof.out -dir=testdata -update AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-TESTFLAG(7)
Man Page