[
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750814#comment-15750814
]
Oleg Ostanin commented on IGNITE-4212:
--------------------------------------
[~dmagda]
Where do you think is the most appropriate place to put a compiled yardstick
module in the apache-ignite binary assembly? We can put it in the libs/optional
along with an others optional libraries or we can create a new directory named
"tools" in the root directory and put "ignite-yardstick" in it.
> Ignite Benchmarking Simplification and Automation
> -------------------------------------------------
>
> Key: IGNITE-4212
> URL: https://issues.apache.org/jira/browse/IGNITE-4212
> Project: Ignite
> Issue Type: Task
> Reporter: Denis Magda
> Assignee: Oleg Ostanin
> Fix For: 2.0
>
>
> There is a plenty of useful Yardstick benchmarks located in ignite-yardstick
> module that is used by the community to check Ignite performance across
> deployments of different configurations.
> However, it's not easy to start with the benchmarking process because the
> user needs to download, build, set up and only after that run the benchmarks.
> The goal of this task is to simplify the process in the following way:
> 1) ignite-yardstick benchmarks have to be pre-compiled and available with
> every Ignite deliverable.
> 2) every deliverable must contain an executable (bat or sh file) with a clear
> instruction on how to start a specific benchmark from the console.
> 3) the executable has use some default yardstick configuration that
> apparently should be AWS oriented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
