Avoid zero timeout in libuv timers (#19810)
Avoid 0 ms timer timeout as it can cause high cpu usage in older versions of libuv
Stelios Fragkakis committed
Mar 10, 2025 at 10:46 UTC
be6f7c2963d562a6a7aec4aa531bbab5d469b057
2 files changed
+2
-2
src/aclk/aclk.c
+1
-1
@@ -872,7 +872,7 @@ void *aclk_main(void *ptr)
872
873
if (schedule_node_update) {
874
worker_is_busy(WORKER_ACLK_NODE_UPDATE);
875
- schedule_node_state_update(localhost, 0);
875
+ schedule_node_state_update(localhost, 10);
876
schedule_node_update = false;
877
}
878
src/health/health_event_loop.c
+1
-1
@@ -669,7 +669,7 @@ static void health_event_loop(void) {
669
"Postponing alarm checks for %"PRId32" seconds, "
670
"because it seems that the system was just resumed from suspension.",
671
(int32_t)health_globals.config.postpone_alarms_during_hibernation_for_seconds);
672
- schedule_node_state_update(localhost, 0);
672
+ schedule_node_state_update(localhost, 10);
673
}
674
675
if (unlikely(silencers->all_alarms && silencers->stype == STYPE_DISABLE_ALARMS)) {