Re: [HTCondor-users] ååïHTCondor-users Digest, Vol 45, Issue 38

[MÃtyÃs Selmeci <matyas@xxxxxxxxxxx>]

Won't that count partial runs, where the job got, say, preempted?

-Mat

On 08/23/17 14:05, John M Knoeller wrote:

The run time (wall time, not cpu time) of a completed job is

Â

CumulativeSlotTime

Â

the _expression_ CompletionDate â JobCurrentStartDate is the run time of the last time the job executed, which for many jobs will be the same as the CumulativeSlotTime

Â

-tj

Â

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of MÃtyÃs Selmeci
Sent: Wednesday, August 23, 2017 9:29 AM
To: htcondor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] ååïHTCondor-users Digest, Vol 45, Issue 38

Â

Someone else can correct me but I think the best way of calculating the run time of a completed job is to look at the difference between its CompletionDate and JobCurrentStartDate. You can get these numbers for a completed job by using the condor_history command, such as:

condor_history <YOUR JOB ID> -af '(CompletionDate - JobCurrentStartDate)'

that will give it to you in seconds. You can also do:

condor_history <YOUR JOB ID> -af 'interval(CompletionDate - JobCurrentStartDate)'

Hope this helps,
-Mat

On 08/22/17 20:52, åä wrote:

Does anyone know howÂtoÂcaculateÂrunÂtimeÂof each condorÂjob? or job run information on execute machine?

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/