[jira] [Comment Edited] (IGNITE-4212) Ignite Benchmarking Simplification and Automation

["Oleg Ostanin (JIRA)" <ji...@apache.org>]

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

Oleg Ostanin edited comment on IGNITE-4212 at 2/9/17 9:47 PM:
--------------------------------------------------------------

Sorry it took so long, but we had to wait until new Yardstick framework release to get rid of ssh connection to localhost. Here is the new version of Ignite release with Yardstick:

https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c


was (Author: oleg-ostanin):
Sorry it took so long, but we had to wait until new Yardstick framework release to get rid of ssh connection to localhost. Here is the new version of Ignite release with Yardstick:

> 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: 1.9
>
>         Attachments: README.txt
>
>
> 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 Ignite, build and set up benchmarks and only after that run them.
> 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 to use some default yardstick configuration. The first configuration should be intented for local execution (multicast IP finder) and the second needs to be AWS oriented.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)