Hello All,

I upgraded one of my servers to the development version (4.2.7p304), mainly so I could play with the new monitoring mechanism. I gather that the default settings for mru are primarily intended to preserve functionality for rate limiting, not for more in-depth statistical analysis, otherwise I'm not certain why maxage would be set at 64 seconds.

Is there any reason not to use the mru functionality for more in-depth client monitoring? Would the extra CPU/RAM hit from maintaining a large database negatively impact time accuracy, or would the only drawback be the increased consumption of system resources?

I've gone with the following settings for now, though I'll certainly scale them back if they will negatively impact the accuracy I'm handing out to my clients:

mru initmem 8
mru incmem 8
mru maxmem 16384
mru mindepth 1000
mru maxage 86400

Another question: Approximately how much memory is consumed by a single mru entry on a 64bit system?

Tim
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to