[
https://issues.apache.org/jira/browse/CASSANDRA-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-13338:
------------------------------------------
Attachment: Throughput_vs_Threads_Combined _true_snapshot_size.png
Percentiles_vs_Threads_Combined_true_snapshot_size.png
Average_Time_vs_Threads_Combined_true_snapshot_size.png
> JMX: EstimatedPartitionCount / SnapshotSize are expensive
> ---------------------------------------------------------
>
> Key: CASSANDRA-13338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13338
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Legacy/Observability
> Reporter: Corentin Chary
> Assignee: Stefan Miklosovic
> Priority: Normal
> Labels: lhf
> Attachments: Average_Time_vs_Threads_Combined_true_snapshot_size.png,
> Percentiles_vs_Threads_Combined_true_snapshot_size.png,
> Throughput_vs_Threads_Combined _true_snapshot_size.png
>
>
> EstimatedPartitionCount / EstimatedRowCount / SnapshotSize seem particularly
> expensive. For example on our system
> org.apache.cassandra.metrics:type=ColumnFamily,name=SnapshotsSize can take as
> much as half a second.
> All this cumulated means that export stats for all your tables (with
> metrics-graphite or jmx_exporter) is going to take quite some time.
> We should certainly try to find the most expensive end points and see if
> there is a way to cache some of the values.
> cc: [~rgerard]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
