Madhavi, We typically refer to workflow components as actors or components (not modules).
A few suggestions: 1) When running from the command line, something prints to stdout how long workflow execution takes, e.g.: 89 ms. Memory: 83008K Free: 19902K (24%) 2) Kepler has a Tools=>Animate at Runtime option which, during execution, will highlight the actor that's currently executing, and can give you a rough idea of how long actors take. 3) The workflow-run-manager module uses the provenance module to show you how long all your executions have taken. You may easily change to workflow-run-manager-2.1.0 using the Module Manager. https://code.kepler-project.org/code/kepler/trunk/modules/workflow-run-manager/docs/workflow-run-manager.pdf 4) Provenance stores a lot of relevant information, including actor run times. You could mine this data yourself: https://kepler-project.org/developers/interest-groups/provenance-interest-group https://code.kepler-project.org/code/kepler/trunk/modules/provenance/docs/ 5) There is also the runtimemonitor module, which can provide stoplights and progress bars on actors: https://kepler-project.org/developers/incubation/kepler-execution-monitoring/archive/kepler-execution-monitoring http://code.kepler-project.org/code/kepler/trunk/modules/runtimemonitor Derik On Jan 31, 2011, at 1:47 AM, Madhavi Tikhe wrote: > Hi, > > Does Kepler reports anything back which will profile the performance of the > individual module in the workflow or the entire workflow? > Something like the time taken by the workflow and individually by the modules > of the workflow, memory consumed, etc. > > If this is possible through UI, is this possible through command line or web > service interface? > > Thanks, > Madhavi > > DISCLAIMER ========== This e-mail may contain privileged and confidential > information which is the property of Persistent Systems Ltd. It is intended > only for the use of the individual or entity to which it is addressed. If you > are not the intended recipient, you are not authorized to read, retain, copy, > print, distribute or use this message. If you have received this > communication in error, please notify the sender and delete all copies of > this message. Persistent Systems Ltd. does not accept any liability for virus > infected mails. > > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
