Hi, I think a question that should be asked, in the spirit of constructive analysis, is why do you want to understand some low level performance metric. For example I wouldn't want to look into metrics around say how many of my GC cycles are full collections without an idea that GC is a throughput or latency problem. What is the high level metric that indicates that you need to tune the JIT compiler?
I'm not saying that you're necessarily wrong to look here but it does seem unusual and I can't help but feel that applications usually have things that are simpler to understand and optimize than JIT compiler threads. On Tue, Jun 21, 2016 at 6:36 AM, Brian Toal <[email protected]> wrote: > Hi all, a few JIT related questions. > > 1) How do I monitor the length of the compiler queues (client and server)? > I want to understand the backlog (if any) to determine if the application > could benefit from more compilation threads. > > 2) What other compilation metrics should I be paying close attention to? > Is there a metric that exposes the proportion of code that is running > interpreted vs native so I have an idea of how warm the system is. > > - Brian > > -- > You received this message because you are subscribed to the Google Groups > "mechanical-sympathy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- regards, Richard Warburton http://insightfullogic.com @RichardWarburto <http://twitter.com/richardwarburto> -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
