KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I am creating a scheduled executor to read the memory usage of the JVM. I have come across two ways to get memory statistics in a running JVM - Runtime & MemoryMXBean, with the following correspondence between their methods: memoryMxBean.getHeapMemoryUsage().getUsed() <=> runtime.totalMemory() - runtime.freeMemory() memoryMxBean.getHeapMemoryUsage().getCommitted() <=> runtime.totalMemory() memoryMxBean.getHeapMemoryUsage().getMax() <=> runtime.maxMemory() With the exception of the additional non-heap memory usage information provided by MemoryMXBean, are there any reasons why I should prefer it over Runtime, or vice-versa?
Tags (comma-separated)
Save Edits
Cancel