| Key: |
QB-2562
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Michael Plank
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 19/Oct/15 09:50 AM
Updated: 13/Jan/17 02:02 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
6.0.28
|
| Fix Version/s: |
7.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
The Grid > active nodes > Heatmap feature is great for Ram + CPU usage.
But often I would just like to figure out, which nodes are "really" doing something.
I measure this by having a look at the running builds of a node.
Builds can have such a small memory footprint or CPU usage, that I don't see in the Ram/CPU heatmap.
Adding a 3rd option to the Heatmap dropdown: "Number of running builds" I could easily check, which VMs are idle at a specific time frame.
|
|
Description
|
The Grid > active nodes > Heatmap feature is great for Ram + CPU usage.
But often I would just like to figure out, which nodes are "really" doing something.
I measure this by having a look at the running builds of a node.
Builds can have such a small memory footprint or CPU usage, that I don't see in the Ram/CPU heatmap.
Adding a 3rd option to the Heatmap dropdown: "Number of running builds" I could easily check, which VMs are idle at a specific time frame. |
Show » |
| There are no comments yet on this issue.
|
|
Number of running builds heatmap