| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8025378 | 8 | Erik Helin | P3 | Resolved | Fixed | b109 |
The performance counters and memory pools for metaspace should report the same data for:
- init
- used
- committed
Since the performance counters has maxCapacity (which means reserved virtual memory) and memory pools has getMax() (which the maximum value), these two properties can't be compared.
- init
- used
- committed
Since the performance counters has maxCapacity (which means reserved virtual memory) and memory pools has getMax() (which the maximum value), these two properties can't be compared.
- backported by
-
JDK-8025378 Metaspace performance counters and memory pools should report the same data
-
- Resolved
-
- relates to
-
JDK-8077987 MaxCapacity for Metaspace for jstat should report MaxMetaspaceSize
-
- Closed
-