Open GoogleCodeExporter opened 9 years ago
I agree, this is a long-standing feature request, and Calabsh's new support for
profiling makes it doable at low cost.
It would be convenient to allow profiling without restarting the fwk. We may
not have to implement a per-job profiling configuration, a system-wide switch
is fine as long as we can turn it on/off dynamically (which is easy with OSGi).
The profiling log should go to the job's log directory, or appear with other
logging statements but easily filterable.
Original comment by rdeltour@gmail.com
on 27 May 2013 at 6:08
Original issue reported on code.google.com by
josteinaj@gmail.com
on 27 May 2013 at 2:31