mikemccand commented on issue #14630: URL: https://github.com/apache/lucene/issues/14630#issuecomment-2900807348
Hmm @yugushihuang (on my team (Amazon product search) team) found this is another way to query the kernel (our Amazon Linux 2 boxes seem not to have `/proc/config.gz`): ``` getconf CLK_TCK ``` The problem is, on `beast3` it gives 100: ``` beast3:util.nightly[main]$ getconf CLK_TCK 100 ``` When the kernel's config says 1000: ``` beast3:util.nightly[main]$ zcat /proc/config.gz | grep HZ CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set # CONFIG_NO_HZ_IDLE is not set CONFIG_NO_HZ_FULL=y CONFIG_NO_HZ=y # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_MACHZ_WDT=m ``` And I'm definitely on the new kernel: ``` beast3:util.nightly[main]$ uname -a Linux beast3.mikemccandless.com 6.14.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 09 May 2025 17:36:18 +0000 x86_64 GNU/Linux ``` Why is `CLK_TCK` different from `CONFIG_HZ`...? There is some [confusing discussion here](https://kernelnewbies.kernelnewbies.narkive.com/7qlZrujb/getconf-clk-tck-and-config-hz)... Hmm it looks like `CLK_TCK` is deprecatedand apps should instead use `sysconf(_SC_CLK_TCK)` -- maybe that gives the right answer (matching CONFIG_HZ at kernel compile time?) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org