On Mon, May 9, 2011 at 9:20 AM, Daniel Lucraft wrote:
> On Monday, 9 May 2011 at 14:58, Thomas E Enebo wrote:
>
> On Mon, May 9, 2011 at 8:16 AM, Daniel Lucraft
> wrote:
>
> * use thread times from ThreadMXBean instead of the global process
> cputime (possibly only when there are multiple jruby
On Monday, 9 May 2011 at 14:58, Thomas E Enebo wrote:
On Mon, May 9, 2011 at 8:16 AM, Daniel Lucraft wrote:
> > * use thread times from ThreadMXBean instead of the global process
> > cputime (possibly only when there are multiple jruby threads as this
> > will slow
> > things down)
> This seems li
On Mon, May 9, 2011 at 8:16 AM, Daniel Lucraft wrote:
> Hi all,
>
> I've got some time to spend on improving the built in profiler support
> soon, and wanted to get some suggestions. Current ideas in rough order
> of priority:
>
> * use thread times from ThreadMXBean instead of the global process
