[
https://issues.apache.org/jira/browse/IGNITE-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154146#comment-15154146
]
ASF GitHub Bot commented on IGNITE-2579:
----------------------------------------
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/500
IGNITE-2579
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-2579
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/500.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #500
----
----
> Investigate HashMap.Node[] allocations from GridCacheMvccManager$3
> ------------------------------------------------------------------
>
> Key: IGNITE-2579
> URL: https://issues.apache.org/jira/browse/IGNITE-2579
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Ilya Lantukh
> Fix For: 1.6
>
>
> *Problem*
> See GridCacheMvccManager.addFuture() method. We create a weird HashSet there
> with internal table size == 5. Can we have something more efficient here?
> *Proposed solution*
> Need to run single get-put benchmarks and check usual size of this
> collection. If it is often equal to 1, then instead of allocating the whole
> collection, we'd better to have a singleton first and expand to collection if
> there are more elements.
> Please pay attention that collection usually used as monitor in some
> synchronized blocks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
