Re: How much do we care about high-load scenarios?

2016-09-13 Thread Chris Johns
On 13/09/2016 16:25, Eric S. Raymond wrote: Not a crazy idea, but I lean against it. My problem is that threading is a serious defect attractor (as we have in fact seen in the async-DNS code). I would not tar all threading architectures and designs with the async-DNS threading code brush. Look

✘minpoll=maxpoll=2

2016-09-13 Thread Gary E. Miller
Yo All! I have some solid results on minpoll=maxpoll=1. That gives a poll time of 2 seconds. When minpoll=maxpoll=0 works Ill be testing that. UNtil thne I'll be testing other values. First, the good news. On a Raspberry Pi 3B, with Uputronics hat, minpoll=maxpoll=1 is much better than minpo

Re: How much do we care about high-load scenarios?

2016-09-13 Thread Eric S. Raymond
Gary E. Miller : > > I'd prefer to bias towards architectural simplicity unless and until > > field reports force us to optimize for the high-load case. > > If NTPsec is to seriously challenge NTP Classic, it must outperform > NTPsec at the bleeding edge. In the NTP case that is high load > facto

Re: NTPsec's longer-term objectives

2016-09-13 Thread Sanjeev Gupta
On Mon, Sep 12, 2016 at 8:14 PM, Eric S. Raymond wrote: > While this is in some ways a tempting thought, I think the energy we > might spend on this would be better directed towards a newer language > that *is* suitable for soft realtime and has good provability properties > for security. Rust o