cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7128) Switch NBHS for CHS on read path
Date Thu, 01 May 2014 12:51:15 GMT

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

T Jake Luciani commented on CASSANDRA-7128:
-------------------------------------------

Yeah interestingly enough they may have just fixed this issue: https://github.com/boundary/high-scale-lib/commit/7baaeaef26e090601fa601862589d402000a3de2

> 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)

Mime
View raw message