ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4212) Ignite Benchmarking Simplification and Automation
Date Tue, 20 Dec 2016 20:22:58 GMT

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

Denis Magda commented on IGNITE-4212:
-------------------------------------

Summarizing the discussion happened on the dev list. Let's reconsider the task a bit.

We need to create "benchmarks" folder and put it under the root of an Apache Ignite distribution.
The structure of this folder is shown below.

apache_ignite_root_folder
-- bin
-- examples
...
-- benchmarks
    — bin (contains scripts needed to run the benchmarks)
    — src (contains benchmarks sources and a pom.xml in order to create a project in an
IDE instantaneously)
    — config (configs for amazon and well as for local benchmarks execution)
    — libs (compiled and ready-to-run benchmarks)
    — README.txt (instructions how to run the benchmarks)

More details can be found here.

> 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 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.4#6332)

Mime
View raw message