[
https://issues.apache.org/jira/browse/IGNITE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229697#comment-15229697
]
Denis Magda commented on IGNITE-2952:
-------------------------------------
Some points from my side.
New package "load" should be created and all load tests should be located in it.
We can start with the following test scenarios:
- IgniteRandomOpLoadTest - will execute a random operation (excluding Scan and
SQL queries) over all configured caches. Among operations we should have one
that will start an explicit transaction with random concurrency/isolation level
and inside of transactions will perform a random operation over all or several
transactional caches that are configured.
- IgniteRandomOpHeapLoadTest - the same as above but only for onheap caches.
- IgniteRandomOpOffHeapLoadTest - the same as above but only offheap caches are
used.
- IgniteRandomOpSwapLoadTest - the same as above but only for caches that has
swap configured.
> 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)
