ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladislav Pyatkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2952) Add yardstick benchmark for cache load testing
Date Sun, 17 Apr 2016 14:19:25 GMT

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

Vladislav Pyatkov commented on IGNITE-2952:

Theank you [~dmagda], 
# I added cahages which allow are generating SQL query automaticly by QueryEntry. Also I had
changed configuration properties and spring xml.
# Really I accidedentally missed points 1 and 2:
## I have added sample in IGNITE-2982, which is not allow to use offheap cache until  bug
has not solved.
## Now only one key is using for same cache, if other is not declared in xml.

Could you please check my last updates?

> Add yardstick benchmark for cache load testing
> ----------------------------------------------
>                 Key: IGNITE-2952
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2952
>             Project: Ignite
>          Issue Type: Test
>    Affects Versions: 1.5.0.final
>            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
> 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

View raw message