In your letter dated Sun, 31 May 2015 13:29:16 +0200 you wrote: >I'm not really sure what you want to do with the data you gather. The result >would be pretty much similar to what the pool monitoring system already >gathers, just as seen from an outsider because you will get a different >server on every measurement. >Ok you can make a statistic about the leap second e.g. to show roughly >how the percentage of servers announcing the leap second is. But is that >all you want to accomplish?
Here are a couple of reasons: - client side monitoring, certainly with an as diverse set of nodes as Atlas probes may reveal all kinds of things normal monitoring doesn't see. - independent reporting is usually appreciated by users of a system - a longer term goal for Atlas, finding out if one-way delay measurements are possible between selected nodes. >Personally I don't mind this, as long as you don't have all 8000 probes >start at once but randomly distribute the load over the 15 minutes. >8000 probes multiplied with 3 packets at once is about 1.7 Megabyte and >could easily annoy servers with weaker links. The spread is expected to be 400 seconds. Tim Bray wrote: >In my head, the atlas probes won't monitor the whole pool. Quite possible. From a client point of view it is usually enough to know what you can expect, this is not meant to replace normal monitoring. >They will just monitor whatever whether you get a good time from the >first pool server that looks up? The probes will perform a DNS lookup each time they perform a measurement, so it depends a bit on what variation the DNS server returns. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
