[ https://issues.apache.org/jira/browse/CASSANDRA-14485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662367#comment-16662367 ]
Benedict commented on CASSANDRA-14485: -------------------------------------- Thanks - while you're here, it's not clear why each value is also preceded by a size? And that we deserialize into a separate buffer? Is there a reason we don't simply deserialize straight from the input stream? We seem to mix and match deserialization from the buffer and the input stream. > Optimize internode messaging protocol > ------------------------------------- > > Key: CASSANDRA-14485 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14485 > Project: Cassandra > Issue Type: Improvement > Components: Streaming and Messaging > Reporter: Jason Brown > Assignee: Jason Brown > Priority: Major > Fix For: 4.0 > > > There's some dead wood and places for optimization in the internode messaging > protocol. Currently, we include the sender's \{{IPAddressAndPort}} in *every* > internode message, even though we already sent that in the handshake that > established the connection/session. Further, there are several places where > we can use vints instead of a fixed, 4-byte integer value- especially as > those values will almost always be less than one byte. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org