I never played much with rados bench but it doesn't seem to have for example
settings for synchronous/asynchronous workloads, thus it probably just
benchmarks the OSD throughput and ability to write to journal (in write mode)
unless you let it run for a longer time.
So when you stop rados bench
When measuring read bandwidth using rados bench, I've been doing the
following:
* write some objects using rados bench write --no-cleanup
* drop caches on the osd nodes
* use rados bench seq to read.
I've noticed that on the first rados bench seq immediately following the rados
bench wri
