[
https://issues.apache.org/jira/browse/IGNITE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716241#comment-14716241
]
Anton Vinogradov commented on IGNITE-1093:
------------------------------------------
Dmitry,
That was first usage or yardstick's restartes.
First of all, I've finished restarters implementation, they worked only
locally, but now supports remote restarts too.
Second problem was that restarter's settings <delay>:<period> are absolute, but
benchmarks warmup delay always depends of setUp phase duration.
In other words in case you use restarters you should have setUp phase duration
the same for all benchmarks at benchmarks set, otherwise you will have shifts
at charts.
Usage of same data size at all benchmarks allowed to fix benchmarks shift
problem.
I'll write additional notes at yardstik manual.
> Rebalancing with default parameters is very slow
> ------------------------------------------------
>
> Key: IGNITE-1093
> URL: https://issues.apache.org/jira/browse/IGNITE-1093
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: sprint-7
> Reporter: Pavel Konstantinov
> Assignee: Anton Vinogradov
> Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: Plot_ThroughputLatencyProbe_01.png, rebalancing.zip
>
>
> # Start one node with partitioned cache with one backup.
> # Load into the cache 40billions of keys using DataStreamer
> # Start second node on the same host
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
