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.
What would you like to be added:
Show peak resource used so far, so user have a chance to know if over reserved resource.
Why is this needed:
Sometime, user may apply 64G memory, but actually it's used only 4G. It wastes resource. With this feature, user has a chance aware of this, and user or admin can take action base on this information.
Taking MII deployment as an example, the memory usage is always a bottleneck. New Jobs are not able to perform because previous jobs used too much memories. Admin would like to know which jobs used too much resources.
Without this feature, how does the current module work:
User has to open metric table, and monitor it.
Components that may involve changes:
The text was updated successfully, but these errors were encountered:
scarlett2018
changed the title
Let user know peak resource of a job.
Need to know Job peak resource value(s)
Jan 9, 2019
scarlett2018
changed the title
Need to know Job peak resource value(s)
Need to surface Job peak resource value(s) to job detail page so that user (admin) can easily know the job's max resource usage in a glance.
Jan 9, 2019
What would you like to be added:
Show peak resource used so far, so user have a chance to know if over reserved resource.
Why is this needed:
Sometime, user may apply 64G memory, but actually it's used only 4G. It wastes resource. With this feature, user has a chance aware of this, and user or admin can take action base on this information.
Taking MII deployment as an example, the memory usage is always a bottleneck. New Jobs are not able to perform because previous jobs used too much memories. Admin would like to know which jobs used too much resources.
Without this feature, how does the current module work:
User has to open metric table, and monitor it.
Components that may involve changes:
The text was updated successfully, but these errors were encountered: