[
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868200#comment-15868200
]
Denis Magda commented on IGNITE-4212:
-------------------------------------
[~oleg-ostanin],
Please update the doc with this text below. I've edited it a bit.
*By default, all the necessary files will be automatically uploaded from the
host in which you run the command above to every other host to the same path.
If you prefer to do it manually set the AUTO_COPY variable in property file to
`false`.*
//I've double checked project compilation and for me it worked fine. Sorry I
did not mention it before. Please attach maven //building logs if you can.
I didn't build the project, I rather opened it with Intellij IDEA and Intellij
IDEA showed me that it can't find these two methods
{code}
cc.setReadThrough(args.isStoreEnabled());
cc.setWriteThrough(args.isStoreEnabled());
{code}
> 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)
