Redhat benchmark tool

Running transaction Preparing : Installing : boost-program-options Installed: fio Here are the common uses of Markdown. Learn more Close. Are you sure you want to request a translation? We appreciate your interest in having Red Hat content localized to your language.

Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated. We are generating a machine translation for this content. For more details about some of the available tools, see this Knowledgebase article. The command will execute a write test and two types of read tests. The --no-cleanup option is important to use when testing both read and write performance.

By default the rados bench command will delete the objects it has written to the storage pool. Leaving behind these objects allows the two read tests to measure sequential and random read performance. Before running these performance tests, drop all the file system caches by running the following:.

To increase the number of concurrent reads and writes, use the -t option, which the default is 16 threads. Also, the -b parameter can adjust the size of the object being written. The default object size is 4MB. A safe maximum object size is 16MB.

Red Hat recommends running multiple copies of these benchmark tests to different pools. Doing this shows the changes in performance from multiple clients. Multiple rados bench commands may be ran simultaneously by changing the --run-name label for each running command instance. The --run-name option is also useful when trying to simulate a real world workload. For example:. Remove the data created by the rados bench command:.

Ceph includes the rbd bench-write command to test sequential writes to the block device measuring throughput and latency. These defaults can be modified by the --io-size , --io-threads and --io-total options respectively.