[
https://issues.apache.org/jira/browse/IGNITE-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859450#comment-15859450
]
Stanilovsky Evgeny edited comment on IGNITE-2577 at 2/9/17 12:54 PM:
---------------------------------------------------------------------
already fixed {code}entries = new LinkedHashSet<>();{code}
was (Author: estanilovsky):
you can close this tiket, already fixed {code}entries = new
LinkedHashSet<>();{code}
> Investigate HashMap.Node[] allocations from GridDistributedTxMapping.add()
> --------------------------------------------------------------------------
>
> Key: IGNITE-2577
> URL: https://issues.apache.org/jira/browse/IGNITE-2577
> Project: Ignite
> Issue Type: Task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Stanilovsky Evgeny
> Priority: Minor
> Labels: performance
> Fix For: 2.0
>
>
> *Problem*
> GridDistributedTxMapping is initialized with empty HashSet() for TX entries
> by default.
> When the very first element is added, undelying HashMap expands causing
> memory traffic.
> *Proposed solutions*
> 1) Use LinkedList instead. One can notice that when GridDistributedTxMapping
> is deserialized using direct reader, "entries" are read as list. Furthermore,
> both "reads" and "writes" projections are returned as wrapped views, so that
> do not benefit form fast lookups.
> If we neither perform lookups from entries, nor require "unique" Set
> semantics, "entries" could be changed to LinkedList thus decresaing memory
> traffic.
> 2) Use special singleton collection. This way we will have to evaluate all
> "entries" usages very carefully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
