-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Feature request) Test against multiple servers #12
Comments
Why not just run multiple containers each with a different SPEEDTEST_HOST and SPEEDTEST_SERVER but all pointing to the same InfluxDB? |
The problem in doing that would be - all speed test instance would run at the same time, will choke the pipe and will lead to inconsistent results. If running one after other then we know for sure that only one test is running a given time. |
You could add some delays in addition:
|
The above delays likely wouldn’t work well since, they could overlap in the future. Likely the better way would be to have a PR for looping through a list of comma-separated SERVER_HOST values but this seems a very specific use case? Changing the delay to be more of a cron-type schedule would also likely help for multiple containers at least |
Please consider adding a feature where we can define multiple speed test server and it tests against those sequentially. One can define the speed test server using the ID.
I would love to have a test report from a couple of servers in India, Europe, US and Singapore.
The text was updated successfully, but these errors were encountered: