You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Lantukh (JIRA)" <ji...@apache.org> on 2016/03/09 11:06:40 UTC

[jira] [Resolved] (IGNITE-2584) Investigate whether GridDhtPartitionTopologyImpl.part2Node could have List as value.

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

Ilya Lantukh resolved IGNITE-2584.
----------------------------------
    Resolution: Not A Problem
      Assignee:     (was: Ilya Lantukh)

> Investigate whether GridDhtPartitionTopologyImpl.part2Node could have List as value.
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-2584
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2584
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>             Fix For: 1.6
>
>
> *Problem*
> "GridDhtPartitionTopologyImpl.part2Node" has value of type Set<UUID>. However, set semantics is almost never used except of node leave events which are pretty rate.
> Iterations over this Set require instantiation of iterators. This could be avoided if we replace HashSet with ArrayList.
> *Proposed solution*
> 1) Investigate whether Set "unique" semantics is exploited anywhere.
> 2) Investigate whether HashSet.get() O(1) is exploited on hot paths.
> 3) If neither p.1 nor p.2 hold - replace HashSet with ArrayList and change corresponding foreach-loops to counted for-loops.



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