GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/2180 IGNITE-5567
Added benchmarks which compare a performance of Ignite.reentrantLock and IgniteCache.lock in three use case.
1) Atomic increment operation.
2) Only get a lock and immediately unlock.
3) Atomic increment over random keys.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/SharplEr/ignite ignite-5567
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2180.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2180
----
commit e724e9042c66e304aba3bb64d343af5dc45f95c3
Author: Alexander Menshikov <
[hidden email]>
Date: 2017-06-21T16:49:44Z
Add benchmark
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---
Locked
