Re: [chrony-dev] New online/offline command

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Thu, May 24, 2018 at 02:11:58PM +0200, Christian Ehrhardt wrote:
> On auto-deployed config changes of virt systems (with plenty of switch
> interfaces for example) I've seen three digits per second (rare, but
> existing).

And each one runs all NM dispatcher scripts? I suspect the bottleneck
is in the execution of the scripts and the chronyc binary, not in
handling of the request in chronyd. It takes just few system calls per
source.

Have you tried profiling?

> second    event
> 1         net event 1 triggers "probe I"
> 2         Events 2-20 trigger 19 more
> ...
> 7         probe I completes and returns to caller "event 1"
> 8         the formerly waiting probe II (just one) runs now
> ...
> 14        probe II completes and returns to all callers Events 2-20
> 
> This is synchronous + batching as I'd think of it

This sounds like a major complication of the code. If I understand it
correctly, chronyd would need to cache responses and check when was a
request received.

> You wrote later:
>   "How about "onoffline" or "maybeonline"?"
> 
> I'd like auto-onoffline or something like it more than any of the two above

That looks better, but would it be correct to call it "auto" when it
works only once when the command is issued and not all the time,
unlike the "auto_offline" option does for instance?

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.