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 2014/04/15 14:50:23 UTC

[jira] [Commented] (CASSANDRA-6755) Optimise CellName/Composite comparisons for NativeCell

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

Benedict commented on CASSANDRA-6755:
-------------------------------------

An ideal solution would probably be modelled on the util.FastByteOperations class

> Optimise CellName/Composite comparisons for NativeCell
> ------------------------------------------------------
>
>                 Key: CASSANDRA-6755
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6755
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>              Labels: performance
>             Fix For: 3.0
>
>
> As discussed in CASSANDRA-6694, to reduce temporary garbage generation we should minimise the incidence of CellName component extraction. The biggest win will be to perform comparisons on Cell where possible, instead of CellName, so that Native*Cell can use its extra information to avoid creating any ByteBuffer objects



--
This message was sent by Atlassian JIRA
(v6.2#6252)