I think you are right. Mondrian should use the &quot;after GC&quot; hook, else, it detects situations where the memory usage is high but the GC can still fix it.<br><br>Would you mind creating a Jira case?<br><br>Thanks for spotting this.<br>

<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 20, 2012 at 9:56 AM, Matt Campbell <span dir="ltr">&lt;<a href="mailto:mkambol@gmail.com" target="_blank">mkambol@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<p>NotificationMemoryMonitor uses
MemoryPoolMXBean.setUsageThreshold() to define the memory threshold for triggering
a notification.<span>  </span>Based on the javadoc for
MemoryPoolMXBean, I think usageThreshold <span> </span>is independent of whether GC has completed.<span>  </span>There’s another threshold that takes GC into
account, though. <span> </span>MemoryPoolMXBean.setCollectionUsageThreshold()
specifies a threshold to be checked after recycling unused objects.</p>

<p>This blog post has a nice example of usage threshold vs.
collection usage threshold:<span>  </span><a href="http://techblug.wordpress.com/2011/07/21/detecting-low-memory-in-java-part-2/" target="_blank">http://techblug.wordpress.com/2011/07/21/detecting-low-memory-in-java-part-2/</a></p>







<p>Is the intention with Mondrian memory monitoring to notify whenever
the memory threshold exceeded, or just post-garbage collection?</p>

<p> </p>



<br>_______________________________________________<br>
Mondrian mailing list<br>
<a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br>
<br></blockquote></div><br></div>