From 591ae9af21a88fde955e13844bb82497b5c76725 Mon Sep 17 00:00:00 2001 From: Madelyn Olson Date: Fri, 7 Feb 2025 13:10:57 -0800 Subject: [PATCH] Increase threshold for info.tcl even higher (#1687) It's possible for the clientCron and the serverCron to get out of sync, so that even though they are both at 100hz, they could be firing independently. (e.g. server cron fires on 5, 15, 25ms and client cron fires at 0, 10, 20ms) So it's actually possible for 2x the number of crons. Signed-off-by: Madelyn Olson --- tests/unit/info.tcl | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tests/unit/info.tcl b/tests/unit/info.tcl index 704d4ad940..29247c28ae 100644 --- a/tests/unit/info.tcl +++ b/tests/unit/info.tcl @@ -340,9 +340,10 @@ start_server {tags {"info" "external:skip" "debug_defrag:skip"}} { if {$::verbose} { puts "instantaneous metrics instantaneous_eventloop_cycles_per_sec: $value" } assert_morethan $value 0 - # Hz is configured to 100, so we expect a value of about 100, but in practice it will be lower - # because of imprecision in kernel wakeups, but we also have some other wakeups like clients cron. - assert_lessthan $value 150 + # Hz is configured to 100, so we expect a value around 200 since there will be 100 wakeups for + # both the server and the clients cron. In practice it will be lower because of imprecision in + # kernel wakeups. + assert_lessthan $value 200 set value [s instantaneous_eventloop_duration_usec] r config set hz 10 if {$::verbose} { puts "instantaneous metrics instantaneous_eventloop_duration_usec: $value" }