ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-2234) GridCacheMvccManager.contextReset() generates garbage.
Date Thu, 31 Mar 2016 11:32:25 GMT

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

Vladimir Ozerov updated IGNITE-2234:
------------------------------------
    Issue Type: Task  (was: Sub-task)
        Parent:     (was: IGNITE-2232)

> GridCacheMvccManager.contextReset() generates garbage.
> ------------------------------------------------------
>
>                 Key: IGNITE-2234
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2234
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Yakov Zhdanov
>              Labels: performance
>             Fix For: 1.6
>
>
> GridCacheMvccManager.contextReset() method operates on a thread-local LinkedList. Only
two operations are used: "add" and "getLast". 
> Once cache op is finished, it is reset - new LinkedList is created. 
> Proposed solution:
> 1) Use TLS (array + index) instead of LinkedList;
> 2) Reset = (set index to 0) + (nullify all previous elements). The latter is needed because
GridCacheMvccCandidate migth contain references to cache entries.



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

Mime
View raw message