[
https://issues.apache.org/jira/browse/CASSANDRA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667825#comment-13667825
]
Jonathan Ellis commented on CASSANDRA-5019:
-------------------------------------------
What makes this a bitch is that we ask our Iterators for Column objects, which
we then add to the ColumnFamily. So we can't just drop in a FlyweightColumns
CF subclass; the damage is already done by then.
We'd have to push the CF into OnDiskAtomIterator and have it call add(name,
value, timestamp) to avoid the Column construction overhead.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
