[
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867459#comment-15867459
]
Oleg Ostanin commented on IGNITE-4212:
--------------------------------------
[~dmagda]
Your version of README.txt says:
"1. These Ignite Yardstick Benchmarks have to be uploaded to every remote host.
The path
to the uploaded benchmarks should be exactly the same on each host."
But now we added the functionality to help user upload Benchmarks from one
remote host or from local machine to every other remote hosts. I think it would
be better if we say:
By default all the necessary files will be automatically uploaded from the host
in which you run the command above to every other host in exact same path. If
you prefer to do it manually set the AUTO_COPY variable in property file to
`false`.
I've double checked compile the project and for me it worked fine. Sorry I did
not mention it before. Please attach maven building logs if you can.
> 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)
