[
https://issues.apache.org/jira/browse/CASSANDRA-19676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-19676:
------------------------------------------
Test and Documentation Plan: ci
Status: Patch Available (was: In Progress)
> Stream processing for StorageProxy::updateCoordinatorWriteLatencyTableMetric
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-19676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19676
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Core
> Reporter: Sam Lightfoot
> Assignee: Sam Lightfoot
> Priority: Normal
> Fix For: 5.x
>
> Attachments: image-2024-06-02-17-25-25-071.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On profiling a write-heavy workload (90% writes) using easy-cass-stress, it
> became very clear StorageProxy::updateCoordinatorWriteLatencyTableMetric was
> a hot path that ~15% of the CPU cycles of
> ModificationStatement::executeWithoutCondition were taken up by (see attached
> async-profiler image).
> We should convert this stream to a simple for loop, as has been discussed
> recently on the mail list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
