[
https://issues.apache.org/jira/browse/IGNITE-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867087#comment-15867087
]
Denis Magda commented on IGNITE-4212:
-------------------------------------
[~oleg-ostanin]
Final notes from my side:
* This issue reported before has not been fixed yet: if to create an
IntellijIDEA project from the sources you will not be able to compile
{{IgniteNode}} class because of the two lines below
{code}
cc.setReadThrough(args.isStoreEnabled());
cc.setWriteThrough(args.isStoreEnabled());
{code}
* I prefer not to mention how to active multiple drivers mode in README. This
should be a straightforward getting started guide. If the user requires
advanced settings he can go to Yardstick page. So, I removed the mentioning of
multiple drivers introduced by you. Please copy the content from the attached
README.
* If it's possible I would put "charts-{DATE}" under "result-{DATE}" folder.
Now they are on the same directory level.
This is all from my side. You got a green light for me. Please take into
account my minor comments and pass the benchmarks for review to [~skozlov].
> 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)
