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

Semen Boikov updated IGNITE-4296:
---------------------------------
    Description: 
These optimizations are possible:
- now on exchange GridDhtPartitionsSingleMessage is processed inside exchange 
future exclusive lock
- GridDhtPartitionTopology.update always creates copies of node2part, part2node 
maps
- it is possible for joning node do not send GridDhtPartitionsSingleMessage 
since we know in advance it does not have any data
- method GridDhtPartitionTopology.update returns map copy which is not actually 
used

  was:
These optimizations are possible:
- now on exchange GridDhtPartitionsSingleMessage is processed inside exchange 
future exclusive lock
-  GridDhtPartitionTopology.update always creates copies of node2part, 
part2node maps
- it is possible for joning node do not send GridDhtPartitionsSingleMessage 
since we know in advance it does not have any data


> Optimize GridDhtPartitionsSingleMessage processing
> --------------------------------------------------
>
>                 Key: IGNITE-4296
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4296
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>             Fix For: 1.9
>
>
> These optimizations are possible:
> - now on exchange GridDhtPartitionsSingleMessage is processed inside exchange 
> future exclusive lock
> - GridDhtPartitionTopology.update always creates copies of node2part, 
> part2node maps
> - it is possible for joning node do not send GridDhtPartitionsSingleMessage 
> since we know in advance it does not have any data
> - method GridDhtPartitionTopology.update returns map copy which is not 
> actually used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to