You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
Short summary about the issue/question: We want to calculate the actual duration time of a job, from the start of the job to the end of the job. We need to exclude the waiting time. At first we use the createdTime, and later we changed to use the appLaunchedTime. But when the job is still in waiting status, the appLaunchedTime appears.
@xianfeng appLaunched just means the app is launched, but it may still wait for resources to really run.
We have not yet record the start timestamp for running state, we may support it in future.
Sorry for this inconvenience.
For a job attempt:
WholeDuration = CompletionTime - StartTime
RunningDuration = CompletionTime - RunTime
WaitingDuration = WholeDuration - RunningDuration
For the whole job which may have multiple attempts:
WholeDuration = CompletionTime - StartTime
RunningTime = Sum_all_attempts (CompletionTime - RunTime)
WaitingDuration = WholeDuration - RunningDuration
Organization Name: Advantech
Short summary about the issue/question: We want to calculate the actual duration time of a job, from the start of the job to the end of the job. We need to exclude the waiting time. At first we use the createdTime, and later we changed to use the appLaunchedTime. But when the job is still in waiting status, the appLaunchedTime appears.
Brief what process you are following:
How to reproduce it:
OpenPAI Environment: Cluster
uname -a
):Anything else we need to know:
The text was updated successfully, but these errors were encountered: