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
CP-53858: Domain CPU ready RRD1 metric - runnable_any
Adding a new metric 'runnable_any' as % of time that at least one vCPU
of the domain is in the runnable state. It is the sum of the following 3
metrics:
- runstate_full_contention
- runstate_concurrency_hazard
- runstate_partial_contention
Naming it 'runnable_any' instead of 'runnable' is to resolve one problem
with rrd2csv: if we name it 'runnable', rrd2csv will select both
RRD1("runnable") and RRD2("runnable_vcpus") when the 'runnable' is used:
> rrd2csv AVERAGE:vm:<vm-uuid>:runnable
> timestamp, AVERAGE:vm:<vm-uuid>:runnable, AVERAGE:vm:<vm-uuid>:runnable_vcpus
This is because "runnable" is a prefix of "runnable_vcpus".
Naming it 'runnable_any', with rrd2csv:
* can select only RRD1 if we use:
rrd2csv AVERAGE:vm:<vm-uuid>:runnable_any
* can select only RRD2 if we use:
rrd2csv AVERAGE:vm:<vm-uuid>:runnable_vcpus
* can select both RRD1 and RRD2 if we use:
rrd2csv AVERAGE:vm:<vm-uuid>:runnable
Naming it 'runnable_any' also makes it clearer as the 'runnable' metric is % of
time that at least one vCPU of the domain is in the runnable state.
Add max to "runnable_any" metric to follow the fix here:
#6493
Signed-off-by: Bengang Yuan <[email protected]>
[Rebase with renaming and one fix]
Signed-off-by: Gang Ji <[email protected]>
0 commit comments