1. Book keeping records consume a lot of memory, especially when large app loads a lot of classes that generate a lot of symbols (each symbol is individually malloc'd)
2. Worker thread may not be able to handle the workload. When that happens, unprocessed book keeping records can consume a large amount of additional memory.
Due to above problems, Native Memory Tracking system trends to shut itself down when it is needed the most.
This RFE is intended to fix the scalability issues in original NMT implementation.
- blocks
-
JDK-8323655 Develop test checking NMT and GC logs for being consistent
- Open
-
JDK-8042469 Launcher changes for native memory tracking scalability enhancement
- Closed
- duplicates
-
JDK-8027713 psr:perf native memory tracking takes 40% of runtime for fusion apps
- Closed
-
JDK-8046288 NMT tests failed with RuntimeException: '...' missing from stdout/stderr
- Closed
-
JDK-8044026 runtime/NMT/JcmdScale.java failed with: java.lang.RuntimeException: 'KB, committed=' missing from stdout/stderr
- Closed
-
JDK-7022526 Add additional info about native memory usage in hs_err report
- Closed
-
JDK-7177408 Dump native memory tracking data to hs_err file
- Closed
-
JDK-8042633 Remove "AutoShutdownNMT" command line flag
- Closed
-
JDK-8046598 Scalable Native Memory Tracking development
- Resolved
- relates to
-
JDK-8042469 Launcher changes for native memory tracking scalability enhancement
- Closed
-
JDK-8042633 Remove "AutoShutdownNMT" command line flag
- Closed
-
JDK-8044140 [TESTBUG] Create NMT (Native Memory Tracking) tests for NMT2
- Closed