> I'm not familiar with how FreeBSD accounts CPU, but NTPsec uses a second
> thread for DNS lookups. If the traffic triggers lots of DNS lookups, the CPU
> gets accounted for in ticks per core and the ticks are fairly long, you could
> probably expect to see about twice the load.
The extra thr
Mike Yurlov via devel writes:
> I recently started the public server for ntppool (Yo, Ask) on
> FreeBSD. Yesterday I was migrate from Classic NTPd to NTPSec (oh, it
> was painful!). I'm copy ntp.conf to ntpsec.conf and only convert
> "magic" 127.127.20 x to refclock. When I looking to "top" I see N
My best guess is that we are now using crypto
quality random numbers where we don't need them. That and nobody has reported
CPU problems yet. You are probably the first one to have enough traffic to
notice. Thanks for the data point.
Hmmm... When I increase mru size, cpu extremely increased
> When I looking to "top" I see NTPsec eat 10-17% CPU. But Classic NTPd eat
> only 4-6% on same average 3-4kpps/queries per second. Why?
I don't have a clean answer. My best guess is that we are now using crypto
quality random numbers where we don't need them. That and nobody has reported
Hi All!
I recently started the public server for ntppool (Yo, Ask) on FreeBSD.
Yesterday I was migrate from Classic NTPd to NTPSec (oh, it was
painful!). I'm copy ntp.conf to ntpsec.conf and only convert "magic"
127.127.20 x to refclock. When I looking to "top" I see NTPsec eat
10-17% CPU. Bu
