cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10309) Avoid always looking up column type
Date Mon, 14 Sep 2015 14:16:46 GMT

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

T Jake Luciani commented on CASSANDRA-10309:
--------------------------------------------

bq.  The type map in SerializationHeader would then just be an array rather than a map.

That sounds like the best option

> Avoid always looking up column type
> -----------------------------------
>
>                 Key: CASSANDRA-10309
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10309
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Priority: Minor
>              Labels: perfomance
>             Fix For: 3.x
>
>
> Doing some read profiling I noticed we always seem to look up the type of a column from
the schema metadata when we have the type already in the column class.
> This one simple change to SerializationHeader improves read performance non-trivially.
> https://github.com/tjake/cassandra/commit/69b94c389b3f36aa035ac4619fd22d1f62ea80b2
> http://cstar.datastax.com/graph?stats=3fb1ced4-58c7-11e5-9faf-42010af0688f&metric=op_rate&operation=2_read&smoothing=1&show_aggregates=true&xmin=0&xmax=357.94&ymin=0&ymax=157416.6
> I assume we are looking this up to deal with schema changes. But I'm sure there is a
more performant way of doing this.



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

Mime
View raw message