You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/04/09 13:04:00 UTC
[jira] [Updated] (IGNITE-4959) Possible slight memory leak in free
list
[ https://issues.apache.org/jira/browse/IGNITE-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk updated IGNITE-4959:
-------------------------------------
Fix Version/s: (was: 2.5)
2.6
> Possible slight memory leak in free list
> ----------------------------------------
>
> Key: IGNITE-4959
> URL: https://issues.apache.org/jira/browse/IGNITE-4959
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 2.0
> Reporter: Ivan Rakov
> Assignee: Alexey Goncharuk
> Priority: Major
> Fix For: 2.6
>
>
> To reproduce, run PageEvictionMultinodeTest (any eviction mode), set ENTRIES to Integer.MAX_VALUE.
> Observations:
> 1) After a few minutes of test running, number of allocated pages looks like a constant (a bit more than eviciton threshold, 90% by default). This is expected behaviour with enabled page eviction.
> 2) More precise measurement shows that there's slow linear growth of allocated pages number, literally 10-20 pages per minute.
> 3) Number of pages with type T_PAGE_LIST_NODE grows, number of all other pages remains constant.
> 4) Though, total number of data pages in free list remains constant (with minor fluctuations).
> We have to find out whether this process has a saturation point, after which pages number stops growing. Otherwise, it's a memory leak and should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)