You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/07/10 07:58:01 UTC
[jira] [Updated] (IGNITE-2084) Yardstick: benchmark-run-all.sh
script should able to deploy and grab logs for distributed environment
[ https://issues.apache.org/jira/browse/IGNITE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-2084:
------------------------------------
Fix Version/s: (was: 2.1)
2.2
> Yardstick: benchmark-run-all.sh script should able to deploy and grab logs for distributed environment
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-2084
> URL: https://issues.apache.org/jira/browse/IGNITE-2084
> Project: Ignite
> Issue Type: Task
> Components: yardstick
> Affects Versions: ignite-1.4, 1.5.0.final
> Reporter: Sergey Kozlov
> Assignee: Yakov Zhdanov
> Fix For: 2.2
>
>
> One of important disadvantages for yardstick framework that it requires to be copied on all hosts where server nodes will run and then server/gc logs can be found on these hosts only .
> But the script bin/benchmark-run-all.sh takes the configuration file where server hosts already defined (config/*.properties). Thus is it possible to add a first step for deploying yardstick on server hosts and then grab logs and copy into local yardstick directory.
> It will significantly reduce time to run benchmarks and get the results faster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)