Hi Pranjul, Currently, Flink only have the metrics shown in taskmanager UI to tell the capacity of JMV overhead. However, Flink cannot detect how much overhead memory has been occupied as those memory footprints might be asked by the third-party library via OS malloc directly instead of via JVM.
Some tools provided by memory allocator such jemalloc or tcmalloc, could help find how much the memory usage via OS malloc. Even though, there still exists some memory used by mmap or on local stack, which is not so easy to detect. Best Yun Tang ________________________________ From: Guowei Ma <guowei....@gmail.com> Sent: Friday, June 25, 2021 15:22 To: Pranjul Ahuja <ahuja0...@gmail.com> Cc: user <user@flink.apache.org> Subject: Re: Metric for JVM Overhaed Hi Pranjul There are already some system metrics that track the jvm status(CPU/Memory/Threads/GC). You could find them in the [1] [1]https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/metrics/#system-metrics Best, Guowei On Fri, Jun 25, 2021 at 2:33 PM Pranjul Ahuja <ahuja0...@gmail.com<mailto:ahuja0...@gmail.com>> wrote: Hi, Is there any metric to track the task manager JVM overhead? Or is it the case that it is already included in the metric Status.JVM.Memory.NonHeap? Thanks, Pranjul
