[ https://issues.apache.org/jira/browse/IGNITE-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039269#comment-16039269 ]
Alexander Menshikov commented on IGNITE-4908: --------------------------------------------- [~amashenkov] ReentrantLock has two hot points: 1) GridCacheLockImpl.Sync#compareAndSetGlobalState() for lock operation. 2) GridCacheLockImpl.Sync#setGlobalState() for unlock operation. In both methods, there are two hottest lines: 1) GridCacheLockState val = lockView.get(key); 2) tx.commit(); So do you want to cache GridCacheLockState somehow? > Ignite.reentrantLock looks much slower than IgniteCache.lock. > ------------------------------------------------------------- > > Key: IGNITE-4908 > URL: https://issues.apache.org/jira/browse/IGNITE-4908 > Project: Ignite > Issue Type: Improvement > Components: data structures > Affects Versions: 1.8 > Reporter: Andrew Mashenkov > Assignee: Alexander Menshikov > Fix For: 2.1 > > > We should make a benchmark and investigate this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)