Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
pepr
on July 13, 2016
|
parent
|
context
|
favorite
| on:
Highly Available Block Storage
What should be used for I/O throughput tests instead?
sciurus
on July 13, 2016
|
next
[–]
One key thing is doing active benchmarking to validate what you're testing. See an example at
http://www.brendangregg.com/ActiveBenchmarking/bonnie++.html
e1ven
on July 13, 2016
|
prev
|
next
[–]
I usually use Bonnie++ when testing disk performance.
http://www.coker.com.au/bonnie++/
notacoward
on July 13, 2016
|
parent
|
next
[–]
The only thing worse than dd is bonnie++. Please, folks, use fio, or at least iozone, with multiple threads and/or a queue depth greater than one.
onnoonno
on July 14, 2016
|
root
|
parent
|
next
[–]
Are you sure? Bonnie++ has byte-wise and block-wise tests. Yes, the byte-wise tests are CPU bound (as expected), but I have not seen that for the block-wise tests on any machine so far?
cthalupa
on July 13, 2016
|
parent
|
prev
|
next
[–]
Bonnie++ is heavily CPU limited and should not be used for disk benchmarking
jdc0589
on July 13, 2016
|
prev
[–]
fio or bonnie++. I've used fio with PerfKitBenchmarker in the past for some cross cloud platform comparisons.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: