FF4J – Feature Flags for Java

Re:FF4J – Feature Flags for Java by ye-olde-sysrq on Wednesday June 07, 2023 @01:58PM (#36230664)

I'm here specifically referring to off-heap memory. I verified this by looking into the jvm with VisualVM. These are objects that aren't part of the normal java heap area and aren't part of garbage collection. The offheap can contain many things - classloaded code, memory-mapped files, direct bytebuffers, and so on. And since it's offheap, it's hard to analyze from Java tooling. So I literally don't know what it was doing.

So in my above scenario, I could indeed run the app with a -Xmx32M and yet the application was still using 200-300MB of resident memory (RSS) due to offheap usage.

[ Parent | on HN ]

Re:FF4J – Feature Flags for Java by NovaX on Wednesday June 07, 2023 @02:48PM (#36231560)

You can use native memory tracking to better inspect offheap usages. I had a similar problem where the default MaxMetaspaceSize was excessive and adjusted it to a reasonable setting.

-XX:NativeMemoryTracking=summary

jcmd <pid> VM.native_memory summary

[ Parent | on HN ]