cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6692) AtomicBTreeColumns Improvements
Date Tue, 18 Feb 2014 01:05:19 GMT

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

Benedict commented on CASSANDRA-6692:
-------------------------------------

Are you sure? It doesn't appear to be applied to trunk, and I can't see the commit message
in my email history

> AtomicBTreeColumns Improvements
> -------------------------------
>
>                 Key: CASSANDRA-6692
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6692
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>              Labels: easyfix, performance
>             Fix For: 2.1
>
>
> There are two improvements to make to the BTree code that should help:
> 1) It turns out Stack Allocation is more rubbish than we had hoped, and so the fast route
actually allocates garbage. It's unlikely this reduces throughput, but the increased young-gen
pressure is probably unwelcome. I propose to remove the fast route for now.
> 2) It is not uncommon to race to perform an update, so that the new values are actually
out-of-date when we come to modify the tree. In this case the update should recognise that
the original (portion of) the tree has not been modified, and simply return it, without allocating
a new one.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message