[
https://issues.apache.org/jira/browse/IGNITE-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869966#comment-15869966
]
Oleg Ostanin commented on IGNITE-4656:
--------------------------------------
[~skozlov]
I think there is no need for adding the `thread_num_dyn_cache_N` parameter
because all the caches are created during setUp method by one thread.
I've added two new parameters to the IgniteBenchmarkArguments class:
additionalCachesNumber - defines how many additional caches will be created
during the setup
additionalCachesName - defines the name of cache which already described in the
xml-configuration. The configuration of this cache will be taken for creation
additional caches.
I've also added the createAdditionalCaches() method to the
IgniteCacheRandomOperationBenchmark class. This method reads the
xml-configuration, finds the cache configuration by name and then creates
additional caches.
> Use dynamic caches for yardstick
> --------------------------------
>
> Key: IGNITE-4656
> URL: https://issues.apache.org/jira/browse/IGNITE-4656
> Project: Ignite
> Issue Type: Task
> Components: yardstick
> Reporter: Sergey Kozlov
> Assignee: Oleg Ostanin
>
> At the moment Yardstick doesn't use dynamic caches and for load tests it is
> significant lack.
> The simplest way to implement looks like to introduce two new options:
> 1. Number of dynamic caches created per thread and named
> _thread_num_dyn_cache_N_
> 2. The name of a cache defined in Ignite Spring XML and its cache
> configuration will be used for dynamic caches created by a thread.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
