[
https://issues.apache.org/jira/browse/CASSANDRA-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039161#comment-13039161
]
Jonathan Ellis commented on CASSANDRA-2681:
-------------------------------------------
bq. Verified compatibility with NonBlockingHashMap. Cassandra may want to
consider adding the java_util_concurrent_chm.jar to the bootclasspath to swap
all CHM usages with NBHM
That falls into the Ugly Hack in my book, since it could lead to subtle
problems elsewhere in Cassandra. Could CLHM provide a constructor taking a
ConcurrentMap instance instead?
> Upgrade ConcurrentLinkedHashMap (v1.2)
> --------------------------------------
>
> Key: CASSANDRA-2681
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2681
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Ben Manes
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0
>
>
> This release has numerous performance improvements. See the change log for
> details.
> It also includes a few useful features that may be of interest,
> - Snapshot iteration in order of hotness (CASSANDRA-1966)
> - Optionally defer LRU maintenance penalty to a background executor (instead
> of amortized on caller threads) (Note that this setting is not advised if
> write storms are not rate limited, since it defers eviction until the
> executor runs.)
> http://code.google.com/p/concurrentlinkedhashmap/
> http://code.google.com/p/concurrentlinkedhashmap/wiki/ExampleUsage
> Verified compatibility with NonBlockingHashMap. Cassandra may want to
> consider adding the java_util_concurrent_chm.jar to the bootclasspath to swap
> all CHM usages with NBHM (CLHM is a decorator on top of CHM).
> http://high-scale-lib.cvs.sourceforge.net/viewvc/high-scale-lib/high-scale-lib/README
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
