You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2017/03/03 17:58:45 UTC

[jira] [Updated] (CASSANDRA-13271) Reduce lock contention for collection types and serializers

     [ https://issues.apache.org/jira/browse/CASSANDRA-13271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Stupp updated CASSANDRA-13271:
-------------------------------------
    Summary: Reduce lock contention for collection types and serializers  (was: Reduce lock contention on instance factories of ListType and SetType)

> Reduce lock contention for collection types and serializers
> -----------------------------------------------------------
>
>                 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)