Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 30 Oct 2013 16:29:27 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12618590.1354553222087.6090.1383150567032@arcas>
In-Reply-To: <JIRA.12618590.1354553222087@arcas>
References: <JIRA.12618590.1354553222087@arcas>
Subject: [jira] [Commented] (CASSANDRA-5019) Still too much object
 allocation on reads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-5019:
-------------------------------------------

Look at ReadVerbHandler; we do need a Row to serialize.

> Still too much object allocation on reads
> -----------------------------------------
>
>                 Key: CASSANDRA-5019
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5019
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Yuki Morishita
>              Labels: performance
>             Fix For: 2.1
>
>
> ArrayBackedSortedColumns was a step in the right direction but it's still relatively heavyweight thanks to allocating individual Columns.


--
This message was sent by Atlassian JIRA
(v6.1#6144)