[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
]
Alexey Goncharuk updated IGNITE-10876:
--
Fix Version/s: 2.8
> "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
> Fix For: 2.8
>
> 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)
[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
]
Alexey Goncharuk updated IGNITE-10876:
--
Ignite Flags: (was: Docs Required)
> "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)
[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)
[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:
Description:
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
was:
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
> "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)
[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel execution
[
https://issues.apache.org/jira/browse/IGNITE-10876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-10876:
Description:
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
was:
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
> "Affinity changes (coordinator) applied" can be executed in parallel execution
> --
>
> 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)
[jira] [Updated] (IGNITE-10876) "Affinity changes (coordinator) applied" can be executed in parallel execution
[ 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 execution (was: Affinity changes (coordinator) applied can be executed in parallel execution) > "Affinity changes (coordinator) applied" can be executed in parallel execution > -- > > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10876) Affinity changes (coordinator) applied can be executed in parallel execution
[ 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 execution (was: finishExchangeOnCoordinator() parallel execution) > Affinity changes (coordinator) applied can be executed in parallel execution > > > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
