[
https://issues.apache.org/jira/browse/CASSANDRA-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20556:
----------------------------------------
Fix Version/s: 4.0.18
4.1.9
5.0.5
5.1
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
Since Version: 4.0.15
Source Control Link:
https://github.com/apache/cassandra/commit/78290bed4518d403407398331673bf35a37c5011
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Unprepared batches unnecessarily measure prepared statement size
> ----------------------------------------------------------------
>
> Key: CASSANDRA-20556
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20556
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.0.18, 4.1.9, 5.0.5, 5.1
>
> Attachments: Screenshot 2025-04-03 at 10.46.07.png,
> ci_summary-1.html, ci_summary-2.html, ci_summary-3.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar-2.gz, result_details.tar.gz
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Running a performance regression test recently, we noticed that unprepared
> batches still call {{{}QueryProcessor.measurePstmnt(){}}}. This is
> unnecessary of course, but wouldn't have been noticeable if it wasn't also
> accounting for about 8% of allocations.
>
--
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
