You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/02/16 21:15:28 UTC

[jira] Commented: (CASSANDRA-799) memtable sort is the bottleneck for range query performance

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

Brandon Williams commented on CASSANDRA-799:
--------------------------------------------

Performance was great with OPP, I saw no penalties with inserts/reads and get_range_slice was as fast as it is without this patch and all tables flushed.  However the RP began giving me timeouts with stress.py as memtables were backing up for flushing.

> memtable sort is the bottleneck for range query performance
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-799
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-799
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: 799.txt
>
>
> The obvious remedy is to use a sorted map.  Unfortunately, keeping the map sorted constantly w/ TreeMap was about 30% slower than HashMap + sort back when we were doing manual locking.  Let's see what the overhead is for ConcurrentSkiplistMap vs NBHM.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.