You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (JIRA)" <ji...@apache.org> on 2018/05/08 17:07:00 UTC

[jira] [Updated] (IGNITE-8458) AffinityAssigment absorbs a lot of java heap

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

Vladislav Pyatkov updated IGNITE-8458:
--------------------------------------
    Description: 
For the more hundred caches and several thousand partitions the size can grow out of 10 Gb.
In my case in heap stored ~5К {{HistoryAffinityAssigment}}, that took nearly 12Gb.

  was:
For the more hundred caches and several thousand partitions the size can grow out of 10 Gb.
In my case heap stored ~5К {{HistoryAffinityAssigment}}


> AffinityAssigment absorbs a lot of java heap
> --------------------------------------------
>
>                 Key: IGNITE-8458
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8458
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>
> For the more hundred caches and several thousand partitions the size can grow out of 10 Gb.
> In my case in heap stored ~5К {{HistoryAffinityAssigment}}, that took nearly 12Gb.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)