cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10232) Small optimizations in index entry serialization
Date Thu, 03 Sep 2015 15:23:46 GMT

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

Ariel Weisberg commented on CASSANDRA-10232:
--------------------------------------------

2.2 is version c right now. 3.0 is version d. I made the change to D as part of [CASSANDRA-8684|https://github.com/apache/cassandra/commit/5baf28d0935b7f112c499856b3bc00c722feb460].
Looking back I am not sure if the change actually impacted the save cache format. 

For CASSANDRA-10155 the cache format has to change. If we don't ship 3.0 with CASSANDRA-10155
saved caches will be broken with 2i. I won't change to E since I already did it to D for 3.0.

> Small optimizations in index entry serialization
> ------------------------------------------------
>
>                 Key: CASSANDRA-10232
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10232
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 3.0.0 rc1
>
>
> While we should improve the data structure we use for our on-disk index in future versions,
it occurred to me that we had a few _very_ low hanging fruit optimization (as in, for 3.0)
we could do for the serialization of our current entries, like using vint encodings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message