New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Measure IO bandwidth & latency #173
Comments
This addresses issue #173. Signed-off-by: Kurt Garloff <kurt@garloff.de>
* Run fio benchmark (disk BW, IOPS, Lat>10ms) This addresses issue #173. * Allow a bit more time to assign names to volumes. * Output Disk bandwidth stats. * Add option -M to run disk benchmarks. * 1.106. Fix calculation of setup & test time, adjust for bench. In particular, we had not accounted the PI benchmark to testing time. This is fixed now (and also assigned the fio disk bench to testing time). The calculation of the maximum cycle time is now dependent on both the pi bench an the disk bench activation. * Fix waiting for fio and detcting success. * Don't output stats name if no stats are available. * Fix logging FIO results to logfile. * Scale IOPS to kIOPS. Rename Grafana fio labels. * Log fio output for logfile. Remove + for fioLat10ms+. * Add fio outputs to benchmark data in dashboard. * Update output of `-h` (help) into README.md * A word on benchmarks. Signed-off-by: Kurt Garloff <kurt@garloff.de>
@garloff Would you rather use the smallest mandatory ssd flavor with Maybe we should even measure both volumes and local storage performance in the future? Currently our mean value for |
Apparently using a ssd flavor for the jumphost with At least the
Compared to a volume root disk instance:
What should I do to make the jumphost use the nova disk? |
With ~1.5% of writes above 10ms latency, you'll see some spurious leader changes with etcd. Probably not yet breaking it, but not very robust either. For the JumpHosts, we currently create a volume manually that we use for booting. We don't do this for the normal VMs (although they do get a volume via nova for diskless flavors). I could add an option to NOT do this, so you can measure local disk performance. |
If I understood correctly with Would there be an easy way to also implement measuring both volume and local storage disk? |
With
|
As for measuring both:
Is this what you want? Maybe we wait for the next generation health monitor from VP12 before adding another three lines... |
Sounds good but for me it would be also okay to wait for the new health mon :) |
We could do something like
fio --rw=randrw --name=test --size=500M --direct=1 --bs=16k --numjobs=4 --group_reporting --runtime=12
and report (average) Bandwidth, IOPs and the percentage of I/O latency > 10ms.
The results could end up in the influxdb/grafana (and of course be reported to the console).
The text was updated successfully, but these errors were encountered: