So my code runs slow ( faster now with 23b15 by 2x but still 2x too slow)
and I was wondering how to look for the issue.
I was going to look for a java profiler but then I remembered a blog by
Rémi on a code coverage monitor
using method handles. So I decided to write my own profiler.
The key c
On Feb 16, 2012, at 8:43 PM, Mark Roos wrote:
> The key code is below and it shows the power of methodHandles is ways one may
> not expect. And it
> added almost nothing to the run time ( maybe a few %). It inserts itself
> into each callsite target and
> collect entry and exit data.
Nice!
