Hi everyone, let me take the opportunity to revive this discussion: I looked into the code and the FLIP-102 proposal for a bit. Bear with me while I'm getting into the topic. 8)
I looked into JDK's ManagementFramework experimenting with the different pools. The Metaspace memory pool is accessible through ManagementFramework's getMemoryPoolMXBeans() method as stated in Andrey's reference [1]. This would mean that we could adapt the current proposal to replace the Nonheap usage pane by a pane displaying the Metaspace usage. This way, we could align the memory usage overview with the memory model getting closer to what's introduced in FLIP-49. This would help removing confusion around the NonHeap term. The only issue I see is that JVM Overhead would still not be represented in the memory usage overview. Best, Matthias [1] https://kb.novaordis.com/index.php/Memory_Monitoring_and_Management_Platform_MBeans#Metaspace -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
