JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-334  -  Provide physical/virtual machine RAM information for nodes and drivers
Posted Sep 24, 2014 - updated Nov 10, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
    Management / Monitoring
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
Currently, the framework does not provide any information on physical/virtual RAM (max, available, committed) or Swap space, nor anything on the RAM usage by the JVM process itself. We propose to add this information to both the JPPFSystemInformation content and the data provided via management (diagnostics MBean)

Previously, I had decided against it, because this information is OS-dependent and would break the cross-platform portability of JPPF. However, it appears this information could be very useful, when available, for job scheduling (via SLA and execution policies) and other purposes, e.g. node provisioning and automated JVM parameters settings. Thus, it can be a very valuable feature. This would also be a very useful building block for the implementation of Feature request JPPF-288 - Clients task sets node configuration

This information and its availability (whether it is supported) shall be provided as part of th feature.

A question is: what kind of support do we want ot give it in the administration console? Should it be a separate panel, or integrated within the existing JVM health panel?

Comment posted by
Nov 10, 07:49
implemented in trunk revision 3464