CPU and Max RSS Analysis tools#2100
Conversation
Fixed bug memory values
Tests added
This comment was marked as resolved.
This comment was marked as resolved.
af6ee22 to
c5f8cb4
Compare
|
We'll get round to this when we can, but a little bit swamped at the moment! |
|
I've had a first look - The "chips" look good:
If nothing has finished the analysis view sticks in this state: I threw a fairly nasty workflow at it and noticed some anomalies: Cannot page through, cannot see tasks I know to have completed. |
|
Oliver recommended the best way to move data around cylc was to use a debug message. Those chips only only appear in dev mode and won't be visible to normal users. |
Using the supercomputer login node as just another computer. We use the term background to mean execution a job in bash without using a job runner like PBS or Slurm. E.g. Warning Irrelevant |
Debug is def the right level to send these messages at, however, I'm not sure we've got the UI to hide debug level messages yet. Orthogonal to this PR either way. |
Remove reference to 'suite' Co-authored-by: Ronnie Dutta <[email protected]>
# Conflicts: # src/views/Analysis.vue
This comment was marked as resolved.
This comment was marked as resolved.
0ed3749 to
f4040f9
Compare
|
Please squash merge |



This apart of 3 pull requests for adding CPU time and Max RSS analysis to the Cylc UI.
This adds the Max RSS and CPU time (as measured by cgroups) to the table view, box plot and time series views.
Linked to;
cylc/cylc-flow#6663
cylc/cylc-uiserver#675
Check List
CONTRIBUTING.mdand added my name as a Code Contributor.setup.cfg(andconda-environment.ymlif present).?.?.xbranch.