You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "vincent royer (JIRA)" <ji...@apache.org> on 2017/03/01 10:36:45 UTC
[jira] [Commented] (CASSANDRA-13271) Reduce lock contention on
instance factories of ListType and SetType
[ https://issues.apache.org/jira/browse/CASSANDRA-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889940#comment-15889940 ]
vincent royer commented on CASSANDRA-13271:
-------------------------------------------
Here is a dedicated repo for this patch : https://github.com/strapdata/CASSANDRA-13271-3.0.11
> Reduce lock contention on instance factories of ListType and SetType
> --------------------------------------------------------------------
>
> Key: CASSANDRA-13271
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13271
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: vincent royer
> Priority: Minor
> Labels: performance
> Fix For: 4.x
>
> Attachments: 0001-CASSANDRA-13271-computeIfAbsent.patch, 0001-CASSANDRA-13271-singleton-factory-concurrency-opimiz.patch
>
>
> By doing some performance tests, i noticed that getInstance() in org.apache.cassandra.db.marshal.ListType and SetType could suffer from lock contention on the singleton factory getInstance(). Here is a proposal to reduce lock contention by using a ConcurrentMap and the putIfAbsent method rather than a synchronized method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)