<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>250MB is about the amount which the GC lets the heap live. And it
grows and shrinks all the time based on the load.</p>
<p>But in the end and start, the lowest point was the same.</p>
<p>And of course, heap requirement is increased when we do the
compression, as we load the rows from the database. That includes
both the metricIds to be compressed as well as the datapoints.<br>
</p>
<p> - Micke<br>
</p>
<br>
<div class="moz-cite-prefix">On 10/11/2016 02:17 PM, Heiko W.Rupp
wrote:<br>
</div>
<blockquote
cite="mid:4D895E6D-CB7E-43EF-B5A4-B9C9A439D66E@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div style="font-family:sans-serif">
<div style="white-space:normal">
<p dir="auto">Hi,</p>
<p dir="auto">On 11 Oct 2016, at 12:57, Michael Burman wrote:</p>
</div>
<div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir="auto">(running for two hours now). It's running between 147MB of memory and 400MB.
</div></blockquote></div>
<div style="white-space:normal">
<p dir="auto">That is a 250MB difference.<br>
Can you try doing a full-gc right before compression start<br>
and right after end to <br>
and measure the heap usage at those points<br>
(before start and at end before gc)<br>
so that we get an idea how much memory<br>
the compression really takes?</p>
<p dir="auto">I started a 0.16 h-services at ~ 10:35, let it
run until 11:13<br>
(first compression happened at 11)<br>
then added 25 feeds - one every 2 minutes. </p>
<p dir="auto">The compression at 1pm went well, but the graph
certainly<br>
shows a much increased need for heap during that time.</p>
<p dir="auto"><img moz-do-not-send="true"
src="cid:F4DB9C04-A766-4C72-B253-73030D4487AB@redhat.com"
alt="" title="Bildschirmfoto 2016-10-11 um 13.13.16.png"></p>
<p dir="auto">We may perhaps try to spread out the compression
over more time and thus trade time for memory<br>
to get rid of this large memory usage peak.</p>
<p dir="auto">After the next crash, I will try to run with
external DB for Inventory to see how much this contributes<br>
to the issue here.</p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
hawkular-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>