Skip to content
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

Closed
simleo opened this issue Jun 23, 2022 · 4 comments
Closed

CQ6 - Workflow running time #14

simleo opened this issue Jun 23, 2022 · 4 comments
Labels
Requirement Something we want to capture in the spec

Comments

@simleo
Copy link
Collaborator

simleo commented Jun 23, 2022

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 like estimatedRunningTime? And do workflow languages have annotation fields for this?

@simleo simleo added the Requirement Something we want to capture in the spec label Jul 6, 2022
@ilveroluca
Copy link
Contributor

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.

@simleo
Copy link
Collaborator Author

simleo commented Oct 14, 2022

This should probably be "How long did this workflow take to 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 startTime from the endTime, so I guess the description for this issue also needs to be clarified.

@simleo
Copy link
Collaborator Author

simleo commented Oct 14, 2022

the description for this issue also needs to be clarified

Done

@simleo
Copy link
Collaborator Author

simleo commented Jan 16, 2023

It only seems useful if accompanied by information on the computing infrastructure used for the run.

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 endTime - startTime is sufficient to get an idea of the order of magnitude. I am therefore closing this as the information is already represented in the profiles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Requirement Something we want to capture in the spec
Projects
None yet
Development

No branches or pull requests

2 participants