Here is the JFR wishlist from 360 Treasury Systems:
"In regards to a "wishlist" for more information: we did have a problem recently with a full code cache and sometimes not compiled code. It is possible to see compilation times in JFR, but I'm missing the details of the -XX:+PrintCompilation. How much L1, L2 compilations we have (-XX:+TieredCompilation). How much percent is called in compiled vs. optimized compiled vs. interpreted methods? How much code cache do we need? Is it worth to activate aggressive optimizations? Does it make sense to tune the inlining (-XX:MaxInlineSize)? Of course no compilation is the worst case, but as the difference between compiled and non-compiled code is very big, more insights are good. There are -XX options for further logging, but it's certainly more painful to analyze them then having it in JFR. I can see the compiled methods, the size, OSR but the question is what conclusions derive from there."

Here is a list from EM:

- 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