[
https://issues.apache.org/jira/browse/IGNITE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699222#comment-14699222
]
Denis Magda edited comment on IGNITE-1128 at 8/17/15 8:59 AM:
--------------------------------------------------------------
Pavel, I ran the following code against the latest Ignite sources and didn't
note any anomaly in heap usage:
{noformat}
public class Main {
public static void main(String[] args) throws Exception {
System.out.println("Postponing node start");
Thread.sleep(30_000);
System.out.println("Starting node");
Ignite node = Ignition.start();
System.out.println("Node started");
}
}
{noformat}
In the attached screenshot (heap_profiling_one_node.png) is what I'm observing
with Visual VM Profiler.
The node was being started right after 12:47 PM and I didn't see any
significant memory usage drop after that even if to press "Perform GC" button.
Nothing changes if the node is started using default-config.xml:
{noformat}
Ignition.start("config/default-config.xml");
{noformat}
Try to use my example as is on your machine. I've a feeling that those 200 MB
of garbage may be produced by other module or JDK.
was (Author: dmagda):
Pavel, I ran the following code against the latest Ignite sources and didn't
note any anomaly in heap usage:
{noformat}
public class Main {
public static void main(String[] args) throws Exception {
System.out.println("Postponing node start");
Thread.sleep(30_000);
System.out.println("Starting node");
Ignite node = Ignition.start();
System.out.println("Node started");
}
}
{noformat}
In the attached screenshot (heap_profiling_one_node.png) is what I'm observing
with Visual VM Profiler.
The node was being started right after 12:47 PM and I didn't see any
significant memory usage drop after that even if press "Perform GC" button.
Nothing changes if the node is started using default-config.xml:
{noformat}
Ignition.start("config/default-config.xml");
{noformat}
Try to load my example as is on your machine. I've a feeling that those 200 MB
of garbage may be produced by other module or JDK.
> 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: Yakov Zhdanov
> 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)
