Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 20 Dec 2016 20:22:58 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13019897.1478800014000.566023.1482265378552@Atlassian.JIRA>
In-Reply-To: <JIRA.13019897.1478800014000@Atlassian.JIRA>
References: <JIRA.13019897.1478800014000@Atlassian.JIRA> <JIRA.13019897.1478800014895@arcas>
Subject: [jira] [Commented] (IGNITE-4212) Ignite Benchmarking Simplification
 and Automation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 20 Dec 2016 20:23:00 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-4212?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D157=
65151#comment-15765151 ]=20

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

Summarizing the discussion happened on the dev list. Let's reconsider the t=
ask a bit.

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

apache_ignite_root_folder
-- bin
-- examples
...
-- benchmarks
    =E2=80=94 bin (contains scripts needed to run the benchmarks)
    =E2=80=94 src (contains benchmarks sources and a pom.xml in order to cr=
eate a project in an IDE instantaneously)
    =E2=80=94 config (configs for amazon and well as for local benchmarks e=
xecution)
    =E2=80=94 libs (compiled and ready-to-run benchmarks)
    =E2=80=94 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-yardst=
ick 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 c=
lear instruction on how to start a specific benchmark from the console.
> 3) the executable has to use some default yardstick configuration. The fi=
rst configuration should be intented for local execution (multicast IP find=
er) and the second needs to be AWS oriented.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)