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-2952) Add yardstick benchmark for cache load testing
Date Wed, 13 Apr 2016 12:49:25 GMT

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

ASF GitHub Bot commented on IGNITE-2952:
----------------------------------------

GitHub user vldpyatkov opened a pull request:

    https://github.com/apache/ignite/pull/640

    IGNITE-2952

        Add yardstick benchmark for cache load testing

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vldpyatkov/ignite ignite-2952

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/640.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 #640
    
----
commit 0d709f1600bad2d174213e6fb0f29b8916528b46
Author: vdpyatkov <vpyatkov@gridgain.com>
Date:   2016-04-13T12:47:08Z

    IGNITE-2952
        Add yardstick benchmark for cache load testing

----


> Add yardstick benchmark for cache load testing
> ----------------------------------------------
>
>                 Key: IGNITE-2952
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2952
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Semen Boikov
>            Assignee: Vladislav Pyatkov
>
> Need implement yardstick benchmark which will be used for cache load testing (add it
in 'yardstick' module).
> For this load testing nodes will be started with several pre-configured caches. Benchmark
on each call of 'test' method should iterate over all configured caches (can get list of caches
using Ignite.cacheNames) and execute some random operations:
> - put(All)
> - get(All)
> - invoke(All)
> - remove(All)
> - putIfAbsent
> - replace
> - scan query
> If cache is transactional it also should execute cache operations inside explicitly start
transaction with random concurrency/isolation mode.
> This benchmark can be run in scenario when server nodes are restarted, so for explicit
transaction need use method IgniteBenchmarkUtils.doInTransaction which has logic for exception
handling.
> It should be possible to pre-load some cache data before starting test , there should
be special benchmark parameter which specifies how many entries load in caches on start (see
IgniteSqlQueryBenchmark.setUp as example of benchmark doing preloading)
> Also it should use non-primitives objects as cache keys/values. Value class should have
String, int, long, double, byte[] fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message