[Mondrian] Memory Monitoring - which threshold?

Luc Boudreau lucboudreau at gmail.com
Tue Nov 20 11:31:54 EST 2012

I think you are right. Mondrian should use the "after GC" hook, else, it
detects situations where the memory usage is high but the GC can still fix

Would you mind creating a Jira case?

Thanks for spotting this.

On Tue, Nov 20, 2012 at 9:56 AM, Matt Campbell <mkambol at gmail.com> wrote:

> NotificationMemoryMonitor uses MemoryPoolMXBean.setUsageThreshold() to
> define the memory threshold for triggering a notification.  Based on the
> javadoc for MemoryPoolMXBean, I think usageThreshold  is independent of
> whether GC has completed.  There’s another threshold that takes GC into
> account, though.  MemoryPoolMXBean.setCollectionUsageThreshold()
> specifies a threshold to be checked after recycling unused objects.
> This blog post has a nice example of usage threshold vs. collection usage
> threshold:
> http://techblug.wordpress.com/2011/07/21/detecting-low-memory-in-java-part-2/
> Is the intention with Mondrian memory monitoring to notify whenever the
> memory threshold exceeded, or just post-garbage collection?
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20121120/ea1df559/attachment.html 

More information about the Mondrian mailing list