JDK-8262165 : NMT report should state how many callsites had been skipped
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-02-23
- Updated: 2021-04-22
- Resolved: 2021-04-19
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 17 |
|---|
17 b19Fixed  |
Related Reports
|
Relates :
|
Description
(This is a breakout from JDK-8261238, which seems to be stuck in review limbo (https://github.com/openjdk/jdk/pull/2428). In order to make that one more concise, I factor out the display changes, which hopefully are non-controversial enough to get upstream easily.) NMT silently omits call sites in its report whose allocation rate is too small to get over a certain, hidden, threshold: - there is a hard wired threshold of 1K in the baseline collector - then, we skip all sites whose size is less than what the unit is (eg scale=G, we skip all allocations < 1G NMT should state how many call sites had been omitted.
Comments
|