master

MMonokaixmetrics: Use milliseconds instead of microseconds as the time unit for scheduling latency

58f95555创建于 2024年9月10日历史提交

文件	最后提交记录	最后更新时间
source	Avoid repeatedly creating links to obtain node metrics Signed-off-by: wangyang0616 <wangyang8126@gmail.com>	2 年前
job.go	to record the start time of job scheduling Signed-off-by: dongge.tan <dontan001@hotmail.com>	4 年前
metrics.go	metrics: Use milliseconds instead of microseconds as the time unit for scheduling latency The current time unit cannot accurately reflect the actual scheduling time like below volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="5"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="10"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="20"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="40"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="80"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="160"} 0 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="320"} 1 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="640"} 1 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="1280"} 68550 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="2560"} 198253 volcano_action_scheduling_latency_microseconds_bucket{action="allocate",le="+Inf"} 243524 volcano_action_scheduling_latency_microseconds_sum{action="allocate"} 5.505664439029926e+08 Signed-off-by: Liang Zheng <zhengliang0901@gmail.com> (cherry picked from commit 2b9b3ddc042bacf2f3705acec1947baf89995ba4) Signed-off-by: Monokaix <changxuzheng@huawei.com>	1 年前
namespace.go	Update author name in boilerplate header to "Volcano" Signed-off-by: Changjian Gao <gaochangjian@gmail.com>	6 年前
queue.go	clean up metrics of deleted objects Signed-off-by: sunxiaofei <sunxiaofei@xiaohongshu.com>	4 年前