You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/05/01 11:47:15 UTC

[jira] [Commented] (CASSANDRA-7128) Switch NBHS for CHS on read path

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

Benedict commented on CASSANDRA-7128:
-------------------------------------

Actually, this points to the fact we should probably update NBHM, separately: [https://github.com/boundary/high-scale-lib/commit/a21a81a9293013233784566bc0e5e83f94d6408a]

> Switch NBHS for CHS on read path 
> ---------------------------------
>
>                 Key: CASSANDRA-7128
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7128
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>            Priority: Trivial
>              Labels: performance
>             Fix For: 2.1 beta2
>
>         Attachments: 7128.txt, Screen Shot 2014-04-30 at 11.07.22 PM.png
>
>
> AbstractRowResolver uses a NBHM for each read request.  
> Profiler flagged this as a bottleneck since the init() call creates a AtomicReferenceFieldUpdater which is stored in a synchronized collection.
> A NBHS is most certainly overkill for such a short lived object.  And turns out switching it to a CHS in my tests yields a ~5-10% read boost.



--
This message was sent by Atlassian JIRA
(v6.2#6252)