[
https://issues.apache.org/jira/browse/IGNITE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703033#comment-14703033
]
Denis Magda commented on IGNITE-1128:
-------------------------------------
You could reproduce this extra 200 MB memory usage because ignite.bat sets the
following heap configuration: -Xms1g -Xmx1g
If to set the same parameters while executing my example from IDEA then we will
reproduce this issue.
Seems that an Ignite node really produces around 200 MB of garbage on startup.
Truly to say I don't have time to investigate further.
Let's return to this issue when there is a real need to optimize memory
consumption on node's startup.
> A single node without any load produces 200MB of garbage
> ---------------------------------------------------------
>
> Key: IGNITE-1128
> URL: https://issues.apache.org/jira/browse/IGNITE-1128
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: sprint-7
> Reporter: Pavel Konstantinov
> Assignee: Denis Magda
> Fix For: ignite-1.4
>
> Attachments: heap_profiling_one_node.png, ig-1128.png
>
>
> Just start one node with default-config.xml
> See attached screenshot from VisualVm.
> If I try to take heap dump from VisualVm it first do GC and heap dump is not
> useful than.
> But in VisualVm memory profiler I see that some arrays of Objects constantly
> generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
