Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
Performance
-
Low Hanging Fruit
-
All
-
None
-
Description
In the current message encoding implementation, it first calculates the `encodeSize` and allocates the bytebuffer with that size.
However, during encoding, it assumes the worst case of writing UTF8 string to allocate bytes, i.e. assuming each letter takes 3 bytes.
The over-estimation further leads to resizing the underlying array and data copy.
Attachments
Issue Links
- causes
-
CASSANDRA-16429 Fix incorrect encoding for strings can be UTF8
-
- Resolved
-
- links to