[
https://issues.apache.org/jira/browse/IGNITE-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826433#comment-16826433
]
Ignite TC Bot commented on IGNITE-10913:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Javadoc]{color} [[tests 0 BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=3700048]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3690255&buildTypeId=IgniteTests24Java8_RunAll]
> Reduce heap occupation by
> o.a.i.i.processors.cache.persistence.file.FilePageStore instances.
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-10913
> URL: https://issues.apache.org/jira/browse/IGNITE-10913
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Assignee: Denis Chudov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With large topology and large amount of caches/partitions and enabled
> persistence could be millions of FilePageStore objects in heap (for each
> partition).
> Each instance has a reference to a File (field cfgFile) storing as String
> absolute path to a partition.
> Also internal File inplementation (on example UnixFile) also allocates space
> for file path.
> I observed about 2Gb of heap space occupied by these objects in one of
> environments.
> Solution: dereference (set to null) cfgFile after object creation, create
> File object lazily on demand when needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
