I think it would be great to see an optional HTTP or SOCKS proxy that the profiler could startup that you could setup your browser (or net based app) to 
use. 

Then, when you're profiling your flows, you'd only see the class / method execution specific to each request. This would save a lot of time and achieve a 
"timeline" type effect, as you rarely want to view all of your data at once. 

This would also allow you to give a breakdown on a package/class/method level (think pie-chart) on how much time of the request was spent where. By 
putting this into a very conceptual view, it makes it easier to understand the results and where you need to focus on faster. 

(ie. X request took 6 seconds total, 4 of them spent in freemarker template compilation, 1 in webwork action and 1 in your actual method). 


This would probably be outside of the scope of this enhancement, but using something like p6spy to proxy the sql requests so you can differentiate 
between slow methods that interface with DAO objects and when you just have a query that needs to be optimized. 

Andrew