[
https://issues.apache.org/jira/browse/CASSANDRA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809182#comment-13809182
]
Jonathan Ellis commented on CASSANDRA-5019:
-------------------------------------------
Hmm, I'm not sure what you're thinking of, but I'm talking about the main
getColumnFamily -> CollationController path where we need to collect Columns
into a ColumnFamily object so we can write them out to the wire. I don't think
local Columns play a large role there. (If they did, couldn't we just avoid
allocating a Column in the first place and just leave the raw fields on the
stack?)
> 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)
