[
https://issues.apache.org/jira/browse/CASSANDRA-19679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Lightfoot updated CASSANDRA-19679:
--------------------------------------
Description:
Part 2 (of 2) of low-hanging fruit Stream improvements.
The second main contributor to allocations and CPU was
SimpleRestriction::bindAndGetClusteringElements, which contributes to 5% of all
allocations for a 50/50 workload.
!image-2024-06-04-21-55-34-457.png!
was:
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.
easy-cass-stress command:
$ bin/easy-cass-stress run KeyValue -n 10m --maxwlat 10 -r 0.1 --rate 20000
--compaction twcs
> Stream processing for SimpleRestriction::bindAndGetClusteringElements
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-19679
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19679
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Core
> Reporter: Sam Lightfoot
> Assignee: Sam Lightfoot
> Priority: Normal
> Fix For: 5.x
>
> Attachments: image-2024-06-04-21-55-34-457.png
>
>
> Part 2 (of 2) of low-hanging fruit Stream improvements.
> The second main contributor to allocations and CPU was
> SimpleRestriction::bindAndGetClusteringElements, which contributes to 5% of
> all allocations for a 50/50 workload.
> !image-2024-06-04-21-55-34-457.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
