No information for the plugin 'memory-monitor' is available. It may have been removed from distribution.
This plugin adds GUI for tracking memory usage on master JVM as well as all connected slave JVMs. This can help you with keeping your Jenkins deployment up and running..
What to look for?
- Eden space and Survivor space are normally small enough in size that you need not consider them unless you manually tweaked their sizes. The graph doesn't capture their relative size difference very well, because it tracks ratio of usage in each pool.
- Some portion of the memory will be occupied by long-living objects, such as jobs, builds, and so on. This will be primarily reflected in the "PS Old Gen" pool of sedimentary memory usage graph. This line must not remain too high for a few hours; it should have some space available to cope with spikes caused when builds are in progress.
- Various data in Jenkins gets lazily loaded, so the "PS Old Gen" pool should start out small then gradually approach to the certain size. This is normal. This curve should be look like
C(1-exp(-Bt)). If instead you see steady linear increase in the sedimentary memory usage graph, that indicates a leak.
Version 1.0 (June 27, 2012)
- Initial release