-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add a graph for scylla_io_queue_flow_ratio #2306
Comments
AFAIU for this metric any aggregation is meaningless. |
@vladzcloudius Naturally, there is no point in summing over it, will Max? Min be helpful? Do you want to filter out values that equal to 1? |
Good point. |
Sorry, still no easy way to play with the sort order in Grafana. I want to include this panel in the next release, but I'm afraid as is, it will not be useful with so many lines in the graph. If we do not have a good idea, I will do it anyhow, but I hope we can come up with something better. If you only care about the outliers I can show the average of everything as a base (maybe per mount point and iogroup) and anything that is outside of let's say two standard deviations (plus some minimal threshold to remove noise) |
@vladzcloudius take a look at my latest comments, if we can't find something better, I'll include a panel with all graphs in it, I'm afraid it will not be useful with clusters with many cores |
This patch adds a panel that shows scylla_io_queue_flow_ratio. Fixes scylladb#2306 Signed-off-by: Amnon Heiman <amnon@scylladb.com>
We probably should think about it a bit more - having a graph for all shards will be quote a hassle indeed. |
I think we should filter all values that are close to 1 (i.e., close to 100%). I'm not sure what the threshold should be but, no point in scrolling throw few hundreds values all of them 1. |
System information
Describe the feature and the current behavior/state.
In light of fixing scylladb/seastar#1641 there was a new metric add:
scylla_io_queue_flow_ratio
.Here is a patch with its description: scylladb/seastar@dd6b20d
Correlating with this value may be helpful when debugging I/O related performance issues.
cc @xemul
The text was updated successfully, but these errors were encountered: