You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Voronkin (JIRA)" <ji...@apache.org> on 2019/01/10 06:40:00 UTC

[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel

     [ https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Voronkin updated IGNITE-10876:
------------------------------------
    Summary: "Affinity changes (coordinator) applied" can be executed in parallel  (was: "Affinity changes (coordinator) applied" can be executed in parallel execution)

> "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
>            Priority: Major
>
> 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)