[Mondrian] Memory Monitoring - which threshold?
mkambol at gmail.com
Tue Nov 20 12:06:11 EST 2012
Thanks Luc. I've created
On Tue, Nov 20, 2012 at 11:31 AM, Luc Boudreau <lucboudreau at gmail.com>wrote:
> 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
>> 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
> Mondrian mailing list
> Mondrian at pentaho.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian