Actions
Bug #12026
closed[crunchstat-summary] gives invalid min_cores recommendation
Start date:
07/24/2017
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Release relationship:
Auto
Description
This recommendation doesn't make sense from a couple of points of view:
### Summary for cwl-runner (su92l-8i9sb-ll9w11siojvlro6) category metric task_max task_max_rate job_total cpu cpus 1 - - # Max CPU time spent by a single task: 1045.15s # Max CPU usage in a single interval: 99.80% # Overall CPU usage: 18.81% #!! cwl-runner su92l-8i9sb-ll9w11siojvlro6 max CPU usage was 100% -- try runtime_constraints "min_cores_per_node":1
It shouldn't recommend a "change" to the same value as is current and it shouldn't recommend a change for max cpu < 100%
Updated by Tom Morris about 7 years ago
- Subject changed from crunchstat-summary gives invalid min_cores recommendation to [crunchstat-summary] gives invalid min_cores recommendation
- Description updated (diff)
Updated by Tom Morris about 7 years ago
I think the problem here was triggered by the fact that there was no cores run-time constraint specified. The job got scheduled on a single core machine (which seems like the right default), but crunchstat-summary contains this code:
used_cores = max(1, int(math.ceil(cpu_max_rate))) asked_cores = self.existing_constraints.get(constraint_key) if asked_cores is None or used_cores < asked_cores: yield ( '#!! {} max CPU usage was {}% -- ' 'try runtime_constraints "{}":{}'
I think perhaps asked_cores should have a default value of 1 if it isn't specified.
Updated by Tom Morris almost 6 years ago
- Target version changed from Arvados Future Sprints to 2019-03-27 Sprint
Updated by Tom Morris almost 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|d23f9c8a99742f116983ce644f25d7ddacfbee4e.
Actions