JDK-8059137 : MemoryPoolMXBeans for different code heaps should contain 'Code heap' in their names
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2014-09-25
- Updated: 2015-06-03
- Resolved: 2014-09-30
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 9 |
|---|
9 b35Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Before segmented code cache was implemented, there was only one MemoryPoolMXBean corresponding to code cache, whose name was 'Code heap'. Now if SegmentedCodeCache is turned on, then there are three mx beans corresponding to different segments, but their names don't include 'Code heap' string: w/o segmented code cache: jdk/bin/java -XX:-SegmentedCodeCache Test Code heap ... w/ segmented code cache: jdk/bin/java -XX:+SegmentedCodeCache Test non-methods profiled nmethods non-profiled nmethods ... I believe that names returned by these beans should contain 'Code heap', because it will make beans naming consistent for both segmented and non-segmented code cache and it will be easier to understand what kind of data is stored in memory regions represented by such beans.
Comments
|