Bug #10570

[crunchstat-summary] should not report 0% CPU and 0 RAM in cases where stats were not reported at all

Added by Tom Clegg almost 3 years ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
11/18/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

Description

Current code produces results like this when there are no usage stats reported at all:

#!! zzzzz-8i9sb-zzzzzzzzzzzzzzz max CPU usage was 0% -- try runtime_constraints "min_cores_per_node":1
#!! zzzzz-8i9sb-zzzzzzzzzzzzzzz max RSS was 0 MiB -- try runtime_constraints "min_ram_mb_per_node":0

Subtasks

Task #14958: Review 14451-crunchstat-summary-cache-ramResolvedTom Morris

Associated revisions

Revision 11d52d78 (diff)
Added by Tom Morris 6 months ago

Don't recommend RAM or CPU changes based on zero usage. refs #10570

Never recommend 0 MB RAM. If CPU usage is zero, don't make any
CPU recommendations.

Arvados-DCO-1.1-Signed-off-by: Tom Morris <>

Revision 8df11bca (diff)
Added by Tom Morris 6 months ago

Don't recommend RAM or CPU changes based on zero usage. refs #10570

Never recommend 0 MB RAM. If CPU usage is zero, don't make any
CPU recommendations.

Arvados-DCO-1.1-Signed-off-by: Tom Morris <>

Revision 701d59fc (diff)
Added by Tom Morris 6 months ago

Don't recommend RAM or CPU changes based on zero usage. refs #10570

Never recommend 0 MB RAM. If CPU usage is zero, don't make any
CPU recommendations.

Arvados-DCO-1.1-Signed-off-by: Tom Morris <>

Revision d23f9c8a
Added by Tom Morris 6 months ago

Merge branch '14451-crunchstat-summary-cache-ram'

Fix three small crunchstat-summary issues:
- Use default of 1 if no cores requested. fixes #12026
- Don't recommend RAM or CPU changes based on zero usage. fixes #10570
- Remove extra MB (2**20) factor in Keep cache recommendation. Fixes #14451

Arvados-DCO-1.1-Signed-off-by: Tom Morris <>

History

#1 Updated by Tom Morris about 2 years ago

  • Target version set to Arvados Future Sprints

#2 Updated by Tom Morris 6 months ago

  • Target version changed from Arvados Future Sprints to 2019-03-27 Sprint

#3 Updated by Tom Morris 6 months ago

  • Assigned To set to Tom Morris

#4 Updated by Tom Morris 6 months ago

  • Status changed from New to In Progress

#5 Updated by Tom Morris 6 months ago

  • Status changed from In Progress to Resolved

#6 Updated by Tom Morris 4 months ago

  • Release set to 15

Also available in: Atom PDF