ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel
Date Tue, 29 Jan 2019 06:29:00 GMT

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

Ignite TC Bot commented on IGNITE-10876:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2930450&amp;buildTypeId=IgniteTests24Java8_RunAll]

> "Affinity changes (coordinator) applied" can be executed in parallel
> --------------------------------------------------------------------
>
>                 Key: IGNITE-10876
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10876
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Voronkin
>            Assignee: Pavel Voronkin
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There is for loop over all cache groups which execution N*P operations in exchange worker
where N is number of cache groups, P is number of partitions.
> We spend 80% of time in a loop
> for (CacheGroupContext grp : cctx.cache().cacheGroups()){
> GridDhtPartitionTopology top = grp != null ? grp.topology() : cctx.exchange().clientTopology(grp.groupId(),
events().discoveryCache());
> top.beforeExchange(this, true, true);
> } 
> I believe we can execute it in parallel



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message