ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1093) Rebalancing with default parameters is very slow
Date Fri, 21 Aug 2015 17:23:46 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707071#comment-14707071
] 

Anton Vinogradov commented on IGNITE-1093:
------------------------------------------

Problem with benchmarcs solved.
Current charts looks good, but still have client operations throughput decreasing almost to
zero at rebalancing.
Idea is to use, for example, only 2X rebalancing ordered listeners at one node. 
X to handle Demand messages and X to handle Supply message.
In this case maximum threads used at rebalancing will be 2X and it should not affects on user
requests so much.

> 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)

Mime
View raw message