Profiling + Indy
rvjansen at xs4all.nl
Fri Oct 14 00:47:30 PDT 2011
there are the DTRACE probes in Java on MacOSX (and Solaris) - you might
want to look into those.
On Fri, 14 Oct 2011 03:52:23 +0000, Charles Oliver Nutter wrote:
> I'm looking to get back into JRuby + Indy work now that the heaviest
> conferences are behind me. Part of this involves running larger
> benchmarks where the hot spots may not be apparent at a glance. In
> order to investigate performance on such benchmarks, I will want to
> some profiling. But what should I use?
> For really egregious problems, the sampling profiler (-Xprof) "sort
> of" works. It's grossly inaccurate when there's no stand-out hotspot,
> but if something is incredibly bad it usually shows it. So that's
> option 1.
> There's -Xrunhprof:cpu=times, which is more accurate, but the impact
> to running code is enormous, there's no way to filter out
> uninteresting code (like JDK core), and I have no idea if it works
> properly with indy (given that there's ongoing work to make JVMTI +
> indy play nice). That's option 2.
> Are either of these options any good? What else do you recommend?
> - Charlie
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
More information about the mlvm-dev