On Tue, Mar 4, 2008 at 2:17 PM, Matt Wagner <[EMAIL PROTECTED]> wrote: > In theory the average offset could be subtracted from individual > offsets when computing score, but that might cause problems of its > own... I just have in mind a quick little sanity check to prevent > freak network failures from emptying the pool.
I think using some high-school-level statistics would be more reliable... compute the standard deviation of offsets, and anything outside of N standard deviations gets kicked out of the pool. Or something like that. You have to presume that the crowd is more knowledgable than the monitoring server about what true time is. I imagine the CPU load on the monitoring server isn't an issue, but rather the network is the bottleneck. The neatest thing to do, IMHO, would be to have each pool member monitor say 10 randomly selected others with noselect, then have the monitoring server use ntpq or some other means to pull in that data and crunch it to determine a score. That is a much bigger job, though. -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
