[
https://issues.apache.org/jira/browse/CASSANDRA-15589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039626#comment-17039626
]
David Capwell commented on CASSANDRA-15589:
-------------------------------------------
bq. keeping histograms on each prepared statement could give us
Is the main difference stats on how the query performed? If so what stats?
> Add histogram to prepared statements and expose as virtual table
> -----------------------------------------------------------------
>
> Key: CASSANDRA-15589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15589
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
> Reporter: Jon Haddad
> Priority: Normal
>
> One of the biggest challenges as an operator is understanding what queries
> are being executed and how long they take. We have the ability to take short
> samples via profileload, but it’s lacking the full diagnostics that keeping
> histograms on each prepared statement could give us. Having this would be a
> massive benefit to most operators as they currently have no idea what
> Cassandra is actually doing.
> Before committing let’s be sure to record some CPU flame graphs to ensure
> there isn’t noticeable performance overhead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
