-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CQ6 - Workflow running time #14
Comments
This should probably be "How long did this workflow take to run?" It only seems useful if accompanied by information on the computing infrastructure used for the run. |
The "does" vs "did" here is similar to the discussion on resource usage in #10: "does" implies a prior knowledge from some statistics while "did" is simply a statement of fact regarding the represented run. The answer to the latter is simply to subtract the |
Done |
Yes, and that's why including a meaningful estimated running time is probably too complicated. That would have to refer to an average system, but what exactly is an average system? Even assuming such a system could be identified, its details would have to be included, but it would need to be clear that they refer to a hypotetical system where the workflow is supposed to run in the specified amount of time, and not to the actual system where the run described in the crate took place. The actual running time given by |
How long does this workflow take to run?
The actual duration of the represented workflow run can be obtained from endTime - startTime on the
CreateAction
. Providing an estimate of the typical running time, on the other hand, is a different thing. Can we use totalTime for that? Or a more specific custom property likeestimatedRunningTime
? And do workflow languages have annotation fields for this?The text was updated successfully, but these errors were encountered: