SPEW(1) | User Commands | SPEW(1) |
spew - measures I/O performance and/or generates I/O load
spew --write|--read|--read-after-write [OPTION]... TRANSFER_SIZE[kKmMgG] FILE
An I/O performance measurement and load generation tool. Writes and/or reads generated data to or from a character device, block device, or regular file.
spew --write -b 16k 1m /tmp/bigfile
or
spew -b 16k 1m /tmp/bigfile
Writes 1 mebibyte (1 mebibyte = 1024*1024 bytes) using 16 kibibytes (1 kibibyte = 1024 bytes) requests to the file /tmp/bigfile using the default pattern (random). Displays the write transfer rate in kibibytes per second and the write transfer time in seconds.
spew --write -u m -i 10 -b 1k 256k /dev/sda1
or
spew -u m -i 10 -b 1k 256k /dev/sda1
Writes 256 kibibytes using 1 kibibyte requests to the block device file /dev/sda1 10 times using the default pattern (random). The iteration and cumulative write transfer rates are displayed in mebibytes per second and the iteration and cumulative write transfer times are displayed in seconds.
spew --raw -d -o 1m -b 16m 1g /tmp/bigfile
or
regorge -s -o 1m -b 16m 1g /tmp/bigfile
Write 1 gibibyte (1 gibibyte = 1024*1024*1024 bytes) starting at an offset of 1 mebibyte using 16 mebibyte requests to the file /tmp/bigfile using the default pattern (random). The data is written synchronously and flushed at file close. Then read in the same data using the same request size and offset. The data is checked to ensure that the data read in matches the data read out. Write and read transfer rates are displayed in kibibytes/second. Read and write transfer times are displayed in seconds.
spew --read -i 0 -u M -p zeros -b 512 1m /dev/zero
or
gorge -i 0 -u M -p zeros -b 512 1m /dev/zero
Read 1 mebibyte of data using 512 byte requests from the file /dev/zero an infinite number of times using the zeros pattern (don't check the data). The iteration and cumulative read transfer rates are displayed in megabytes (1 megabyte = 1,000,000 bytes) per second and the iteration and cumulative read transfer times are displayed in seconds.
spew --raw -g -r -b 1k -B 256K 1t /dev/md1
or
regorge -g -r -b 1k -B 256K 1t /dev/md1
Write 1 tebibyte (1 tebibyte = 1024*1024*1024*1024 bytes) using 1-256 kibibyte requests to the block device /dev/md1 using the random pattern. Random seeks are performed before each transfer, but each block between the start and end of the data is written exactly once. The request sizes are chosen randomly. Then read in the same data using the same request sizes and seeks in the same sequence. Repeat the above sequence an infinite number of times until told to quit (via signal or TUI command).
The data is checked to ensure that the data read in matches the data read out. A curses-based TUI is used to display iteration and cumulative transfer rates, transfer times, and bytes transferred. Display verbose statistics after quitting.
The following algorithm is used to determine blocksize when MAX_BUFFER_SIZE > MIN_BUFFER_SIZE:
Find the largest blocksize that is a power of 2 and is >= MAX_BUFFER_SIZE. Call this maxbuffersize. Find the smallest buffersize that is a power of 2 and is >= MIN_BUFFER_SIZE. Call this minbuffersize. Chunksize = maxbuffersize * (difference in number of bits between min and maxbuffersize + 1). The number of chunks is TRANSFER_SIZE/chunksize. Call this numchunks. There will be numchunks number of read/writes that are of size maxbuffersize, 2 * numchunks number of read/writes that are of size maxbuffersize/2, 4 * numchunks number of read/writes that are of size maxbuffersize/4, and so on until minbuffersize is reached. MIN_BUFFER_SIZE is used for any remaining transfers if TRANSFER_SIZE is not evenly divisible by chunksize.
Example: Using a MIN_BLOCK_SIZE of 1k, a MAX_BLOCK_SIZE of 8k and a TRANSFER_SIZE of 264k results in 8 8k read/writes, 16 4k read/write, 32 2k read/writes, and 64 + 8 1k read/writes.
Use the following od(1) command to examine spew generated files where a data integrity problem has occurred:
od -A d --format=d8 --width=32 <file>
Written by Andrew Patterson <andrew.patterson@hp.com>
Report bugs to Andrew Patterson <andrew.patterson@hp.com>.
Copyright 2007 Hewlett-Packard Corp.
May 2010 | spew 1.0.8 |