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-7116) Use ConcurrentLinkedQueue instead of NonBlockingHashSet in AbstractRowResolver
Date Wed, 30 Apr 2014 17:00:20 GMT

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

Benedict commented on CASSANDRA-7116:
-------------------------------------

Heh, whoops, snuck that past even myself :)

CLQ is maybe slightly better because no biased lock revocation is necessary. But it's probably
much of a muchness.

> Use ConcurrentLinkedQueue instead of NonBlockingHashSet in AbstractRowResolver
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7116
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7116
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Trivial
>             Fix For: 2.1 rc1
>
>         Attachments: 7116.txt
>
>
> There's no reason to use a NBHM in this class, as we only add unique elements. A CLQ
seems a more appropriate lightweight datastructure to use



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

Mime
View raw message