You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/04/03 18:04:13 UTC

[jira] Created: (CASSANDRA-50) expunge ConcurrentHashMap

expunge ConcurrentHashMap
-------------------------

                 Key: CASSANDRA-50
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Jonathan Ellis
         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch

Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-50) expunge ConcurrentHashMap

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-50.
-------------------------------------

    Resolution: Fixed

> expunge ConcurrentHashMap
> -------------------------
>
>                 Key: CASSANDRA-50
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch
>
>
> Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CASSANDRA-50) expunge ConcurrentHashMap

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-50:
------------------------------------

    Attachment: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch

> expunge ConcurrentHashMap
> -------------------------
>
>                 Key: CASSANDRA-50
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch
>
>
> Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CASSANDRA-50) expunge ConcurrentHashMap

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695480#action_12695480 ] 

Johan Oskarsson commented on CASSANDRA-50:
------------------------------------------

Forgot to mention, all tests pass, including testGetCompactionBuckets

> expunge ConcurrentHashMap
> -------------------------
>
>                 Key: CASSANDRA-50
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch
>
>
> Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CASSANDRA-50) expunge ConcurrentHashMap

Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695479#action_12695479 ] 

Johan Oskarsson commented on CASSANDRA-50:
------------------------------------------

>From what I've read on the mailing list and glancing over this code the patch gets a +1 from me.

> expunge ConcurrentHashMap
> -------------------------
>
>                 Key: CASSANDRA-50
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch
>
>
> Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CASSANDRA-50) expunge ConcurrentHashMap

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-50:
---------------------------------------

    Assignee: Jonathan Ellis

> expunge ConcurrentHashMap
> -------------------------
>
>                 Key: CASSANDRA-50
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-50
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>         Attachments: 0001-expunge-ConcurrentHashMap-in-favor-of-NonBlockingHas.patch
>
>
> Avinash says it is less memory-efficient than NonBlockingHashMap.  NBHM also has better performance numbers, although we don't use any of these instances in high-contention scenarios.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.