[kepler-users] How to get the System execution Time for workflows

[Derik Barseghian]

Luis,

Yes, if you're interested in execution time at that level of precision, you don't want to use the Workflow Run Manager.
I've filed your enhancement request: http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5571

Derik


On Feb 2, 2012, at 7:08 AM, Luís Assunção wrote:

> Dear Derik and Matt
> 
> Thanks for your help.
> I have installed the workflow Run Manager and I got the execution Time, but
> unfortunately only hour, minutes, seconds. In some experiments milliseconds
> are important.
> As my initial suggestion and Derik agreed I think it is nice and useful to
> give de execution time, including milliseconds (System.
> currentTimeMillis()), in Runtime Window after "execution finished".
> If this simple feature will be in next Kepler releases I believe that many
> people will like that.
> 
> Regards
> Luis Assuncao
> 
> 
> -----Original Message-----
> From: Derik Barseghian [mailto:barseghian at nceas.ucsb.edu] 
> Sent: quarta-feira, 1 de Fevereiro de 2012 20:36
> To: Luís Assunção
> Cc: kepler-users at kepler-project.org Users
> Subject: Re: [kepler-users] How to get the System execution Time for
> workflows
> 
> Using the Reporting suite is a good approach, but do note that provenance
> recording adds time to workflow executions.
> Other options, like using the WallClockTime actor, are mentioned here:
> http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2009-March/000721.
> html
> I agree that it would be nice if execution time were more apparent. Rather
> or in addition to putting it in the Runtime window, I think having it appear
> after the "execution finished." text at the bottom of each window would be
> useful.
> 
> Derik
> 
> On Feb 1, 2012, at 12:17 PM, Matt Jones wrote:
> 
>> Luis --
>> 
>> If you install the optional Reporting suite, it includes a Workflow Run
> Manager which provides a listing of all of your workflow runs, and includes
> the execution time for each run along with a lot of other useful
> information, as well as the ability to archive runs, return to earlier runs,
> and other useful features. Some screenshots of this are shown in the
> documentation for the Workflow Run Manager:
>> 
> https://code.kepler-project.org/code/kepler/trunk/modules/workflow-run-manag
> er/docs/workflow-run-manager.pdf
>> 
>> Matt
>> 
>> On Wed, Feb 1, 2012 at 10:42 AM, Luís Assunção <lass at isel.ipl.pt> wrote:
>> Hi
>> 
>> 
>> 
>> Sometimes is helpful to get the execution time  of a workflow
> (milliseconds like System.currentTimeMillis()) with hundreds/thousands of
> iterations.
>> 
>> Someone can tell me if it a easy way to get the execution time ?
>> 
>> If not I would like to suggest a small feature that I think will be
> appreciate by kepler-users – In Runtime Window when appear that workflow was
> finished why don´t put the system interval, i. e., The Director get System.
> currentTimeMillis() when Start firing Actors and get the end time when
> finished?
>> 
>> 
>> 
>> Any help or comments will be welcome.
>> 
>> 
>> 
>> Regards
>> 
>> Luis Assuncao
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at kepler-project.org
>> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>> 
>> 
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at kepler-project.org
>> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>