ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5567) Make benchmark Ignite.reentrantLock vs IgniteCache.lock
Date Thu, 22 Jun 2017 13:28:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059386#comment-16059386

ASF GitHub Bot commented on IGNITE-5567:

GitHub user SharplEr opened a pull request:



    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:


To 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 <sharplermc@gmail.com>
Date:   2017-06-21T16:49:44Z

    Add benchmark


> Make benchmark Ignite.reentrantLock vs IgniteCache.lock
> -------------------------------------------------------
>                 Key: IGNITE-5567
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5567
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: data structures
>            Reporter: Alexander Menshikov
>            Assignee: Alexander Menshikov
>             Fix For: 2.1
> Ignite.reentrantLock slower than IgniteCache.lock. First of all, we must create a benchmark
for agreeing about use-case which we want to test.

This message was sent by Atlassian JIRA

View raw message