[
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851982#comment-15851982
]
Denis Magda commented on IGNITE-4212:
-------------------------------------
* {{Building the project}} section says that {{Please look for the building
instructions in `DEVNOTES.txt`}}. However, the devnotes are located under
"source" folder. They either have to be placed under "benchmarks" folder or the
documentation has to say that they are under "sources" folder.
* Documented property {{config/benchmark-atomic-put.properties}} is missing.
Can't check benchmarks execution as README says.
* If to follow the instructions and execute {{`./bin/benchmark-run-all.sh`}}
then I see this error all the time
{code}
<11:14:35><yardstick> Starting driver config '...eTxBenchmark -sn IgniteNode
-ds RELEASE-tx-invoke-1-backup' on localhost with id=0
ssh: connect to host localhost port 22: Connection refused
ssh: connect to host localhost port 22: Connection refused
ssh: connect to host localhost port 22: Connection refused
{code}
* Why do I need this?
{{NOTE: You need to configure ssh key-based authentication to localhost for
running benchmarks on your local machine.}}
I've edited the README file. Please copy-paste all the content from the
attached one in this ticket. I'll review and edit {{Running Ignite Benchmarks
Remotely}} section after the issues above are resolved.
> 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.15#6346)
