[
https://issues.apache.org/jira/browse/CASSANDRA-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Konstantinov updated CASSANDRA-20166:
--------------------------------------------
Change Category: Performance
Complexity: Normal
Component/s: CQL/Interpreter
Fix Version/s: 5.0.x
Status: Open (was: Triage Needed)
> Avoid ByteBuffer allocation during decoding of CQL write requests
> -----------------------------------------------------------------
>
> Key: CASSANDRA-20166
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20166
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
> Reporter: Dmitry Konstantinov
> Assignee: Dmitry Konstantinov
> Priority: Normal
> Fix For: 5.0.x
>
> Attachments: image-2024-12-26-17-33-39-031.png,
> image-2024-12-26-17-35-05-485.png
>
>
> A lot of ByteBuffer objects are allocated when we decode CQL queries,
> frequently the space spent for such objects is large than the actual amount
> of data received.
> There was a similar optimization done some time ago when a Mutation object is
> receiving during a Cassandra cross-node communication: CASSANDRA-15393
> While a complete replacement of ByteBuffer with byte[] during CQL decoding
> step looks very complex task (ByteBuffer is a part of too many entities
> involved into CQL parsing) we can optimize 20% of logic to get 80% of benefit
> by focusing only on batch and modification request types when we have a lot
> of cells are ingested into Cassandra via CQL interface.
> !image-2024-12-26-17-33-39-031.png!
> !image-2024-12-26-17-35-05-485.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
