Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <2041537500.320801266359729244.JavaMail.jira@brutus.apache.org>
Date: Tue, 16 Feb 2010 22:35:29 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-799) memtable sort is the bottleneck
 for range query performance
In-Reply-To: <1069875033.310481266347728522.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

FLUSH-SORTER-POOL and MEMTABLE-POST-FLUSHER seems to both stack equally.

> 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-unbounded-flushwriter.txt, 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.