cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5019) Still too much object allocation on reads
Date Wed, 30 Oct 2013 16:25:35 GMT


Benedict commented on CASSANDRA-5019:

Major overhaul, so suggested with caution, but why don't we pass a context that knows what
to do with the results, and is furnished with them as they are found by the CollationController?
There's no real need to construct a Row at any point - in fact it looks like it gets translated
straight into a List<List<ByteBuffer>> at the end anyway.

> Still too much object allocation on reads
> -----------------------------------------
>                 Key: CASSANDRA-5019
>                 URL:
>             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

View raw message