On Wed Aug 27 2025, Miroslav Lichvar wrote: > On Tue, Aug 26, 2025 at 02:59:12PM +0200, Sebastian Andrzej Siewior wrote: >> The benchmark is about > 1k packets/ second while in reality you have >> less than 20 packets a second. > > I don't want to argue about which use case is more important, but it's > normal for NTP servers to receive requests at much higher rates than > that. In some countries, public servers get hundreds of thousands of > packets per second. A server in a local network may have clients > polling 128 times per second each. > > Anyway, if anyone is still interested in finding out the cause of > the regression, there is a thing I forgot to mention for the > reproducer using ntpperf. chronyd needs to be configured with a larger > clientloglimit (e.g. clientloglimit 100000000), otherwise it won't be > able to respond to the large number of clients in interleaved mode > with a HW TX timestamp.
Yeah, I realized that myself while testing :). The default clientloglimit is too low. Thanks, Kurt
signature.asc
Description: PGP signature
