[ 
https://issues.apache.org/jira/browse/CASSANDRA-19676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Lightfoot updated CASSANDRA-19676:
--------------------------------------
    Description: 
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:

$ bin/easy-cass-stress run KeyValue -n 2000k --maxwlat 10 -r 0.1 --rate 5000 
--compaction twcs

 

  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.


> 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: after.png, image-2024-06-02-17-25-25-071.png
>
>          Time Spent: 0.5h
>  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.
> easy-cass-stress:
> $ bin/easy-cass-stress run KeyValue -n 2000k --maxwlat 10 -r 0.1 --rate 5000 
> --compaction twcs
>  



--
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

Reply via email to