[jira] [Commented] (CASSANDRA-8959) More efficient frozen UDT, tuple and collection serialization format

["Avi Kivity (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600853#comment-17600853 ] 

Avi Kivity commented on CASSANDRA-8959:
---------------------------------------

If you're changing the representation in the native protocol, please make it negotiated, so an old driver can continue talking to a new node, and so that new and old nodes can coexist.

> More efficient frozen UDT, tuple and collection serialization format
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-8959
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8959
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Core
>            Reporter: Aleksey Yeschenko
>            Priority: Normal
>              Labels: performance
>             Fix For: 4.x
>
>
> The current serialization format for UDTs has a fixed overhead of 4 bytes per defined field (encoding the size of the field).
> It is inefficient for sparse UDTs - ones with many defined fields, but few of them present. We could keep a bitset to indicate the missing fields, if any.
> It's sub-optimal for encoding UDTs with all the values present as well. We could use varint encoding for the field sizes of blob/text fields and encode 'fixed' sized types directly, without the 4-bytes size prologue.
> That or something more brilliant. Any improvement right now is lhf.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org