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/02/26 08:06:44 UTC

[jira] [Updated] (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:all-tabpanel ]

vincent royer updated CASSANDRA-13271:
--------------------------------------
    Attachment: 0001-CASSANDRA-13271-singleton-factory-lock-optimization.patch

> 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: 3.0.x, 3.11.x
>
>         Attachments: 0001-CASSANDRA-13271-singleton-factory-lock-optimization.patch
>
>
> By doing some performance tests, i notice that getInstance() in org.apache.cassandra.db.marshal.ListType and SetType could suffer from lock contention on the singleton factory pattern. Here is a proposal to reduce lock contention by using a ConcurrentMap and the putIfAbsent method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)