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

Family timing information. #1524

Closed
hjoliver opened this issue Jul 2, 2015 · 3 comments
Closed

Family timing information. #1524

hjoliver opened this issue Jul 2, 2015 · 3 comments

Comments

@hjoliver
Copy link
Member

hjoliver commented Jul 2, 2015

Another user request:

Currently families show no timing information in cylc. Would it be possible to add this? T-submit & T-start would come from the first task in that family to startup; T-finish from the last to finish.
[and ...] we could see how long an entire cycle took to complete.

I'm not sure this would be very useful at whole-cycle level, but it would be good for task families.

@hjoliver hjoliver added this to the later milestone Jul 2, 2015
@matthewrmshin
Copy link
Contributor

Timing and other metrics can be very useful for questions such as:

  • What are the total and elapsed times consumed by a cycle?
    • ... for jobs submitted to a given batch system?
  • And for other resources, if they are collectable.

@hjoliver
Copy link
Member Author

hjoliver commented Jul 8, 2015

This isn't trivial as task families are virtual - currently we don't actually know when a family is finished at a particular cycle point, because family syntax is expanded in terms of member tasks when the suite is parsed, and hierarchy information is only retained as means grouping whichever members (at a particular cycle point) happen to be present in the task pool.

@hjoliver
Copy link
Member Author

Closing as superseded by #1894

@matthewrmshin matthewrmshin removed this from the later milestone Nov 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants