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.
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.
Attachments
Issue Links
- relates to
-
JDK-8261238 NMT should not limit baselining by size threshold
-
- Resolved
-
