| Key: |
QB-3651
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Steve Luo
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 19/Dec/20 09:45 AM
Updated: 21/Dec/20 12:57 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
10.0.30
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
When the build agent node is very busy, the graph shows < 4%.
The build configuration is hitting the vm hard and cpu usage on the vm shows > 90%
From the code for v10, it shows QB is reporting sys cpu usage.
com.pmease.quickbuild.plugin.measurement.core.supplier.CpuMetricsSupplier
return sysInfo.getCpuUsage().getSys();
OSHI Docs: SYSTEM = CPU utilization that occurred while executing at the system level (kernel).
We would like it should show combined (overall/total CPU usage)
return sysInfo.getCpuUsage().getCombined()
|
|
Description
|
When the build agent node is very busy, the graph shows < 4%.
The build configuration is hitting the vm hard and cpu usage on the vm shows > 90%
From the code for v10, it shows QB is reporting sys cpu usage.
com.pmease.quickbuild.plugin.measurement.core.supplier.CpuMetricsSupplier
return sysInfo.getCpuUsage().getSys();
OSHI Docs: SYSTEM = CPU utilization that occurred while executing at the system level (kernel).
We would like it should show combined (overall/total CPU usage)
return sysInfo.getCpuUsage().getCombined() |
Show » |
| No work has yet been logged on this issue.
|
|
CPU graph shows little to no activity when VM is very busy