On Mon, May 9, 2011 at 8:16 AM, Daniel Lucraft <[email protected]> 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 > cputime (possibly only when there are multiple jruby threads as this > will slow > things down)
This seems like a really useful improvement. Second best (and a very close second) in the list in my opinion (behind API toggling). > * document the code and fix up the specs to be run as part of the build > * restore the old profiler for flat mode (much faster) > * add an HTML output mode I think it should be put in a format which can be transformed (dare I say the format????). At a bare minimum, it should be well-formed HTML to allow transformation. XHTML-like for easy viewing, but still a data format so people can re-purpose the data for other types of display. > * make it possible to turn the API on and off during a Jruby process > execution (will need help with this one) I think this one will be killer. Targeting what you want to measure is really nice. Profiling all of Rails startup to just try and profile where a controller is spending time can be a bit much. A Question...If you toggle on and off and on and off..will it throw away previous results or will it accumulate them? (I imagine the answer could be both) One reason for asking is that I might want to demarcate a method to toggle on and off at the methods boundaries. After 1000 invocations, it would be nice to see the cumulative result. > > Any other requests or ideas, or different opinions on what is important? -Tom -- blog: http://blog.enebo.com twitter: tom_enebo mail: [email protected] --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
