Benedict resolved CASSANDRA-5019.

    Resolution: Duplicate

Since the read path will be rewritten as part of efforts to introduce 
CASSANDRA-7447 (both regards internal APIs, and the implementation details for 
the new format), this ticket should be addressed by "doing things right" here. 
This may mean the legacy format continues to be somewhat inefficient, but this 
may or may not eventually be retired entirely, so there is probably not much 
point spending a lot of time optimising it, esp. when the impact is unknown and 
probably not dramatic in relation to the other costs associated with this 

> 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
>              Labels: performance
>             Fix For: 3.0
> 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

Reply via email to