Thanks @paulgear for clarification. Your message saved me from some typing.
I believe Leo might have an incentive to show that his NTP server equipment can handle the full 100Mbps line capacity. Yes, we have seen that it can do that, mission accomplished, great. Take a screenshot as an evidence, publish it somewhere for others to see and then, maybe, think of all this from the NTP Pool and its users’ point of view.
When someone queries the pool, they generally expect a response. If the query gets directed to a server which can’t handle the query, that’s bad. I think some of you guys are barking at the wrong tree. The monitoring server is doing its job just fine. If despite all tunables that you can tune the servers get too much traffic, that traffic should be spread to a larger area. That is not the monitoring server’s job, but it’s still within the NTP Pool’s problem area.
Now some maths. Based on the CSV log the score of 126.96.36.199 was >= 10 around 45% of the time. If the server can serve 400 million requests per hour when it’s in the pool and maybe 200 million requests per hour when it’s out (based on the above graphs that Leo posted), you will end up handling 24 * ( 0.45 * 400 + 0.55 * 200 ) = 6960 million requests each day. That’s quite a lot already, I might add. These might not be exact figures, but please bear with me.
Now if you tried to follow my suggestion to try to keep the traffic below the 100Mbit line speed to better keep its score >= 10, the daily amount of traffic served by your server might actually increase. If after this change your server was included in the pool for 95% of the time, you would reach the same amount of daily traffic with only an average of 295 million queries per hour (6960 - 200 * 24 * 0.05) / (24 * 0.95). The 200 in that calculation is the amount of hourly traffic while out of the pool, same as in the previous calculation. That way you would not drop as much packets as before, and you would still serve the same amount of daily traffic. If you manage to tweak the netspeed settings so that you’d actually send more than that without hitting your line speed, say, at 350M responses per hour, that’d be even better for the pool.
I’d also like to point out that at this particular moment the netspeed setting is indeed effective. One of my servers (set to 384kbps) that serves exclusively the .cn zone currently pushes out packets at an average of around 30k qps (averaged over the last 14 hours), with 5 min peaks of around 65k qps. That is easily within the limits of a 100Mbps connection, so you can stay under 100Mbps if you want. It’s up to you, the tunables are there for you.
Edit 1 + 2: fixed/refined maths, sorry.