JDK-8066818 : add com.sun.management.CompilationMXBean
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2014-12-05
  • Updated: 2024-07-04
  • Resolved: 2024-07-04
Related Reports
Cloners :  
Relates :  
Description
In order to be able to extend the CompilationMXBean functionality for HotSpot specific attributes we should add an internal interface com.sun.management.CompilationMXBean.  Some possible attributes are:

- Code Cache usage
- Is compiler shut down?
- Access to sweeper data
- Compiled method hotness ranking (query per method, query top N)
- Content of code cache

Comments
Closing. This is an old issue and does not likely represent what compilation information should be added/change in JMX or anywhere else. See also JDK-8328618 about removing HotSpotInternal MBeans.
04-07-2024

[~allwin], can you assign this to an engineer?
23-03-2015

Can you give concrete examples?
10-02-2015

We can live w/o knowing that the method is inline, but we need to know that the method is in the cache (even if inlined). This would be something that we could show to customers and also allow us to warn them against instrumenting (BCI) those methods.
05-02-2015

Why do you need inlined methods? I don't see an easy solution to list all the methods in an array and tell which are normal methods and which are inlined.
05-02-2015

Yes, an array of the methods (including the inlined ones) that are in code cache.
05-02-2015

What data do you want for "Content of code cache"? An array or list of all the methods in the code cache?
05-02-2015

That would be best. Then all involved parties have access to the information.
27-01-2015