You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/08/12 11:29:46 UTC
[jira] [Comment Edited] (CASSANDRA-9894) Serialize the header only
once per message
[ https://issues.apache.org/jira/browse/CASSANDRA-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693211#comment-14693211 ]
Benedict edited comment on CASSANDRA-9894 at 8/12/15 9:29 AM:
--------------------------------------------------------------
Thanks. I've ninja fixed what was an obvious rebase error, that I should have never made (but should have been caught by CI. GTK it definitely will be post CASSANDRA-9673 (it's also possible I missed another new non-flakey dtest failure when checking))
was (Author: benedict):
Thanks. I've ninja fixed what was an obvious rebase error, that I should have never made (but should have been caught by CI). GTK it definitely will be post CASSANDRA-9673 (it's also possible I missed another new non-flakey dtest failure when checking)
> Serialize the header only once per message
> ------------------------------------------
>
> Key: CASSANDRA-9894
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9894
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Benedict
> Fix For: 3.0 beta 1
>
>
> One last improvement I'd like to do on the serialization side is that we currently serialize the {{SerializationHeader}} for each partition. That header contains the serialized columns in particular and for range queries, serializing that for every partition is wasted (note that it's only a problem for the messaging protocol as for sstable we only write the header once per sstable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)