Develop test checking NMT and GC logs for being consistent.
There are at least two mechanisms of tracking memory usages in VM:
Native Memory Tracking (-XX:NativeMemoryTracking=summary -XX:+UnlockDiagnosticVMOptions -XX:+PrintNMTStatistics)
And GC logging (-Xloggc:gclog -XX:+PrintGCDetails)
There should be a test checking that two logs contain consistent data.
VMSQE test base used to contain tests of such type:
metaspace/flags/compareGCLogAndNMT
metaspace/flags/checkMetaspaceSize
But those tests were removed as result of fix of INTJDK-7610947.
If their original sources are attached.
The major reason, why they were removed - they failed due to (JDK-8011548 which was closed as will not fix) and it was not easy to fix those tests.
As stated inJDK-8011548, NMT2 will contain better diagnostic, so when NMT2 is implemented (planned within JDK9 scope) it will make sense to develop tests checking two logs for consistency.
There are at least two mechanisms of tracking memory usages in VM:
Native Memory Tracking (-XX:NativeMemoryTracking=summary -XX:+UnlockDiagnosticVMOptions -XX:+PrintNMTStatistics)
And GC logging (-Xloggc:gclog -XX:+PrintGCDetails)
There should be a test checking that two logs contain consistent data.
VMSQE test base used to contain tests of such type:
metaspace/flags/compareGCLogAndNMT
metaspace/flags/checkMetaspaceSize
But those tests were removed as result of fix of INTJDK-7610947.
If their original sources are attached.
The major reason, why they were removed - they failed due to (
As stated in
- is blocked by
-
JDK-8028541 Native Memory Tracking enhancement
-
- Closed
-
- relates to
-
JDK-8011548 NMT: does not take into account class space of metaspace
-
- Closed
-