[
https://issues.apache.org/jira/browse/IGNITE-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136914#comment-15136914
]
ASF GitHub Bot commented on IGNITE-2333:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/462
IGNITE-2333
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-2333
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/462.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #462
----
commit 3a15b9514209d2f334985393e38bcadea733205b
Author: Ilya Lantukh <[email protected]>
Date: 2016-02-08T12:52:42Z
ignite-2333 : StripedCompositeReadWriteLock.
commit b96539de3a1db9fb77bbdab968ef30d92ef04594
Author: Ilya Lantukh <[email protected]>
Date: 2016-02-08T13:01:56Z
ignite-2333 : Minors.
----
> Hotspot in GridDhtPartitionTopologyImpl readLock() and readUnlock() methods
> ---------------------------------------------------------------------------
>
> Key: IGNITE-2333
> URL: https://issues.apache.org/jira/browse/IGNITE-2333
> Project: Ignite
> Issue Type: Sub-task
> Components: cache, general
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Ilya Lantukh
> Fix For: 1.6
>
>
> When running simple PUT benchmark in ATOMIC cache, read lock-unlock consumes
> up to 10% of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
