Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 15 Sep 2015 16:55:45 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12863899.1442242252000.343742.1442336145908@Atlassian.JIRA>
In-Reply-To: <JIRA.12863899.1442242252000@Atlassian.JIRA>
References: <JIRA.12863899.1442242252000@Atlassian.JIRA>
 <JIRA.12863899.1442242252100@arcas>
Subject: [jira] [Updated] (CASSANDRA-10316) Improve ColumnDefinition
 comparison performance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict updated CASSANDRA-10316:
---------------------------------
         Reviewer: 601126228506
    Fix Version/s:     (was: 3.0.x)
                   3.0.0 rc1

> Improve ColumnDefinition comparison performance
> -----------------------------------------------
>
>                 Key: CASSANDRA-10316
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10316
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>             Fix For: 3.0.0 rc1
>
>
> We have already improved the performance here for the basic comparison, however since these happen exceedingly frequently we may as well go a little (easy step) further. This is a really tiny patch, and we should aim to include before GA, but not RC.
> Right now we use all of an int for the metadata presorting, but in fact we only need 2-3 bytes for this. We can upcast the int to a long, and use the remaining bits to store the prefix of the _name_. This way, a majority of comparisons become a single long comparison. Which will be considerably cheaper.


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