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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/12/29 10:00:57 UTC

[jira] [Updated] (IGNITE-2315) GridSpinReadWriteLock doesn't give any performance benefit

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

Vladimir Ozerov updated IGNITE-2315:
------------------------------------
    Issue Type: Sub-task  (was: Task)
        Parent: IGNITE-2232

> GridSpinReadWriteLock doesn't give any performance benefit
> ----------------------------------------------------------
>
>                 Key: IGNITE-2315
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2315
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.6
>
>
> Quick benchmarking shows that GridSpinReadWriteLock doesn't have any advantages over regular ReentrantReadWriteLock. 
> Both implementation suffers severe drop in throughput under contention because they both CASes the same memory address.
> If we really want to make it faster than ReentrantReadWriteLock, at the very least we should stripe it properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)