[PR #242] [CLOSED] Add lower "netspeed" values #255

New issue

Closed

opened 2026-02-28 14:16:50 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 14:16:50 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/abh/ntppool/pull/242
Author: @PoolMUC
Created: 11/3/2024
Status: ❌ Closed

Base: main ← Head: allow-lower-netspeed

📝 Commits (1)

b121e28 Add lower "netspeed" values

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 docs/manage/tpl/manage/server.html (+1 -1)

📄 Description

To make it easier for servers to join "underserved" zones, i.e., zones where the client/server ratio is such that less powerful servers (or network infrastructure/traffic quota/available bandwidth/...) would easily get overwhelmed even at the current lowest setting of "512 Kbit".

Recent example: https://community.ntppool.org/t/the-issue-of-ntp-requests-exceeding-bandwidth-load/3588

But also, e.g., https://www.ntppool.org/scores/47.236.162.36/, which is in monitoring mode only because it is limited to roughly 1Mbit/s of bandwidth, which would be easily exceeded in this zone even at the "512 Kbit" netspeed setting.

The proposed values are obviously somewhat arbitrary, and different values could be chosen instead. Except the lowest value should hopefully cover the first example above, and the highest new value should hopefully cover the second example. And then some values in between.

Obviously, those values don't make much sense in zones that are not underserved, and achieving the actually intended share will work less well the smaller the netspeed value (in relation to the sum of netspeeds configured for the zone).

And even in underserved zones, lower values might still result in traffic peaks that may overwhelm the server/infrastructure/traffic quota/available bandwidth/... But that would hopefully then be short peaks only, and allow at least some more servers to join an underserved zone (though not all, as there will still be servers that still will be challenged by the traffic load/traffic load peaks).

A refined approach could be to tailor the netspeeds offered to the zone a server resides in. I.e., underserved zones would have additional lower netspeeds available, better served zones will have just the current set. A wide range of how granular this could be is conceivable. However, to start, maybe keep it simple, and make this additional set of netspeeds conditional on the continent zone (vs. individual country zones) only, e.g., zones in Asia are typically underserved, maybe also Africa and South America.

Unfortunately, I don't understand enough about how the website works to make a more specific proposal for the latter refinement myself.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/abh/ntppool/pull/242 **Author:** [@PoolMUC](https://github.com/PoolMUC) **Created:** 11/3/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `allow-lower-netspeed` --- ### 📝 Commits (1) - [`b121e28`](https://github.com/abh/ntppool/commit/b121e2867f70b005c8fe7b0ef074e15120a01b42) Add lower "netspeed" values ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/manage/tpl/manage/server.html` (+1 -1) </details> ### 📄 Description To make it easier for servers to join "underserved" zones, i.e., zones where the client/server ratio is such that less powerful servers (or network infrastructure/traffic quota/available bandwidth/...) would easily get overwhelmed even at the current lowest setting of "512 Kbit". Recent example: https://community.ntppool.org/t/the-issue-of-ntp-requests-exceeding-bandwidth-load/3588 But also, e.g., https://www.ntppool.org/scores/47.236.162.36/, which is in monitoring mode only because it is limited to roughly 1Mbit/s of bandwidth, which would be easily exceeded in this zone even at the "512 Kbit" netspeed setting. The proposed values are obviously somewhat arbitrary, and different values could be chosen instead. Except the lowest value should hopefully cover the first example above, and the highest new value should hopefully cover the second example. And then some values in between. Obviously, those values don't make much sense in zones that are not underserved, and achieving the actually intended share will work less well the smaller the netspeed value (in relation to the sum of netspeeds configured for the zone). And even in underserved zones, lower values might still result in traffic peaks that may overwhelm the server/infrastructure/traffic quota/available bandwidth/... But that would hopefully then be short peaks only, and allow at least _some more_ servers to join an underserved zone (though not all, as there will still be servers that still will be challenged by the traffic load/traffic load peaks). A refined approach could be to tailor the netspeeds offered to the zone a server resides in. I.e., underserved zones would have additional lower netspeeds available, better served zones will have just the current set. A wide range of how granular this could be is conceivable. However, to start, maybe keep it simple, and make this additional set of netspeeds conditional on the continent zone (vs. individual country zones) only, e.g., zones in Asia are typically underserved, maybe also Africa and South America. Unfortunately, I don't understand enough about how the website works to make a more specific proposal for the latter refinement myself. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>