It's really common for users to tweak nzbget configuration in case things go wrong. Everyone is happy if nzbget is downloading everything fine, but if you are going down the rabbit hole of optimizing it, making sure you get completion and good speed from your news server, your internet - it's not very easy.
We already added Disk tests and NewsServer tests to easily see problems related to disk performance and news server, internet speed is logical missing piece.
And competitors have a similar feature too.
Implementation
Let's continue expanding STATUS page since it's a place where you can see your environment and all test results. A simple "Internet Speed test" feature, showing the latest result (similar to disk/server tests) if there is any, ability to start/retry the test, and visually show if it is still in progress. With or without popup element on test start - whatever is easier to implement with the current UI restrictions.
For the algorithm, we could do something similar to what CF speedtest does, it's fast (<30 seconds) and shows reasonable numbers.
Is there already an issue for this request?
Platform
All
Describe the enhancement you'd like
Reasoning
It's really common for users to tweak nzbget configuration in case things go wrong. Everyone is happy if nzbget is downloading everything fine, but if you are going down the rabbit hole of optimizing it, making sure you get completion and good speed from your news server, your internet - it's not very easy.
We already added Disk tests and NewsServer tests to easily see problems related to disk performance and news server, internet speed is logical missing piece.
And competitors have a similar feature too.
Implementation
Let's continue expanding STATUS page since it's a place where you can see your environment and all test results. A simple "Internet Speed test" feature, showing the latest result (similar to disk/server tests) if there is any, ability to start/retry the test, and visually show if it is still in progress. With or without popup element on test start - whatever is easier to implement with the current UI restrictions.
For the algorithm, we could do something similar to what CF speedtest does, it's fast (<30 seconds) and shows reasonable numbers.
Extra information
No response