Arch Linux

Unlike the "linux" package, linux-lts does not define CONFIG_HZ_300 in .config.

Instead the 100Hz frequency is chosen, which maximally optimizes throughput at the expense of latency.

Maybe it would be better to go for 300 Hz if linux-lts is not aimed specifically for servers?

See the kconfig help:


─ Timer frequency

Allows the configuration of the timer frequency. It is customary
to have the timer interrupt run at 1000 Hz but 100 Hz may be more
beneficial for servers and NUMA systems that do not need to have
a fast response for user interaction and that may experience bus
contention and cacheline bounces as a result of timer interrupts.
Note that the timer interrupt occurs on each processor in an SMP
environment leading to NR_CPUS * HZ number of timer interrupts
per second.

Prompt: Timer frequency
Location:
-> Processor type and features

┌── 100 HZ
│
│ CONFIG_HZ_100:
│
│ 100 Hz is a typical choice for servers, SMP and NUMA systems
│ with lots of processors that may show reduced performance if
│ too many timer interrupts are occurring.
│
│ Symbol: HZ_100 [=n]

┌── 250 HZ
│
│ CONFIG_HZ_250:
│
│ 250 Hz is a good compromise choice allowing server performance
│ while also showing good interactive responsiveness even
│ on SMP and NUMA systems. If you are going to be using NTSC video
│ or multimedia, selected 300Hz instead.

┌── 300 HZ
│
│ CONFIG_HZ_300:
│
│ 300 Hz is a good compromise choice allowing server performance
│ while also showing good interactive responsiveness even
│ on SMP and NUMA systems and exactly dividing by both PAL and
│ NTSC frame rates for video and multimedia work.

┌── 1000 HZ
│
│ CONFIG_HZ_1000:
│
│ 1000 Hz is the preferred choice for desktop systems and other
│ systems requiring fast interactive responses to events.