Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 10 Feb 2017 20:55:42 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13019897.1478800014000.51575.1486760142473@Atlassian.JIRA>
In-Reply-To: <JIRA.13019897.1478800014000@Atlassian.JIRA>
References: <JIRA.13019897.1478800014000@Atlassian.JIRA> <JIRA.13019897.1478800014895@jira-lw-us.apache.org>
Subject: [jira] [Updated] (IGNITE-4212) Ignite Benchmarking Simplification
 and Automation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 10 Feb 2017 20:55:46 -0000


     [ https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Magda updated IGNITE-4212:
--------------------------------
    Attachment: DEVNOTES.txt

> 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: benchmark-remote.properties, benchmark-remote-sample.properties, DEVNOTES.txt, ignite-remote-config.xml, 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)