You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2016/01/29 16:16:39 UTC
[jira] [Commented] (IGNITE-2502) GridNearAtomicUpdateRequest
allocates to much Object[]
[ https://issues.apache.org/jira/browse/IGNITE-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123569#comment-15123569 ]
Dmitriy Setrakyan commented on IGNITE-2502:
-------------------------------------------
How about creating ArrayLists of the accurate size and *only* if we need them. Is it possible?
> GridNearAtomicUpdateRequest allocates to much Object[]
> ------------------------------------------------------
>
> Key: IGNITE-2502
> URL: https://issues.apache.org/jira/browse/IGNITE-2502
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> *Problem*
> GridNearAtomicUpdateRequest might create up to 4 ArrayList's. Initially they are empty. When the very first element is added, ArrayList is extended to hold 10 objects (new Object[]). Put in ATOMIC cache almost all operations are performed on a single key.
> As a result 90% of array is not used.
> *Proposed solution*
> We know in advance how many keys participate in operation. Let's use min(10, keyCount) as initial array list size. This will make allocation more accurate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)