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 2016/02/09 07:27:18 UTC
[jira] [Resolved] (IGNITE-2316) Replace GridSpinBusyLock with
improved version of GridStripedSpinBusyLock
[ https://issues.apache.org/jira/browse/IGNITE-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov resolved IGNITE-2316.
-------------------------------------
Resolution: Won't Fix
Profiling didn't show any benefit even in local benchmarks. Hence, closing as "Won't fix".
Implementation is attached. May be we will back to it later.
> Replace GridSpinBusyLock with improved version of GridStripedSpinBusyLock
> -------------------------------------------------------------------------
>
> Key: IGNITE-2316
> URL: https://issues.apache.org/jira/browse/IGNITE-2316
> Project: Ignite
> Issue Type: Sub-task
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
> Attachments: GridStripedSpinBusyLock.java
>
>
> 1) GridStripedSpinBusyLock is not striped properly at the moment - produced AtomicIntegers are located too close to each other to produce considerable amount of false-shares. To fix it, int state of each lock should be padded with dummy values. This will give significant throughput increase.
> 2) Then GridSpingBusyLock must be replaced with GridStripedSpinBusyLock all over the project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)