search

fatty- / daisy-pipeline

Automatically exported from code.google.com/p/daisy-pipeline
0 stars 0 forks source link

Script profiling #320

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be really handy to be able to run a script in "profiling mode" and get 
back some information on which parts of the script takes the most time.

Calabash 1.0.9 added support for profiling:
https://github.com/ndw/xmlcalabash1/commit/806d5cd16434cf5e2c707167bac7518b14ee9
28a

I'm not sure what would be simplest to implement; for each job individually or 
for all jobs. It should be possible to retrieve the profiling log for each job 
separately.

What do you think?

Original issue reported on code.google.com by josteinaj@gmail.com on 27 May 2013 at 2:31

GoogleCodeExporter commented 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