Description
The scheduling latency is not recorded correctly, it is smaller than actual values. Because not every scheduling cycle will generate allocations, when the cycle could not generate an allocation and it skips most of the steps, in that case, the latency is almost 0. We should only track the latency when there is actually an allocation generated.
Attachments
Issue Links
- is duplicated by
-
YUNIKORN-877 Fix the scheduling latency metrics
-
- Closed
-