These are chat archives for HotswapProjects/user
The problem is, when I instrument my hot methods, my code gets instrumented perfectly but takes a lot of time (I guess the C1 compiler bails out and interpreter starts again).
Is there any way of restricting the JVM to use the compiler even after the instrumentation (If that is causing the actual overhead)?
Can I use any other strategy to get the profiler's feedback to instrument hot methods so that I don't get any overhead after instrumentation?
I have checked my agent with ClassFileLoadHook event at class load time and it works perfectly without any overhead.