Reputation: 5861
I came across async-profiler which helps to analyze Unsafe.allocatememory calls happening in context of DirectByteBuffer and drill down who are the callers, using the flamegraph output.
Unfortunately async-profiler doesn't support Windows, since Windows lacks few aspects which linux provides.
How do I go about analyzing the native memory requests which are happening , for example, off-heap analysis.
I tried using Native Memory Tracking, but this tool only focuses on JVM usage of offheap memory and not any third party libraries.
But our application uses third party libraries which internally uses DirectByteBuffers.
I have inspected with MBeans the amount of direct buffer memory used, but this piece of information doesn't give me any idea what's happening below the hood, especially for Windows.
I have started using ProcessExplorer, VMMap, but honestly I am just getting started, so if someone has already experienced in this area, with Windows, how to analyze the issue, basically I want to find out and optimize the usage of off-heap by 3rd party libraries, in Windows environment.
Upvotes: 0
Views: 12