You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that server.DownloadTest and server.UploadTest use a hard coded image size (which essentially drives the bandwidth impact of these tests) to dlSizes[3] and ulSizes[3].
I am using the GO API to write a simple program that periodically runs speedtest on a regular basis. I'd like to reduce the size of each download/upload test to reduce overall bandwidth consumption since it will be run on an ongoing basis. Recognizing the is likely a tradeoff between test size/bandwith impact and accuracy, but it would be great if the developer could evaluate that tradeoff rather than rely on the hardcoded values currently provided.
The text was updated successfully, but these errors were encountered:
Hi, @cirne. I think reduce the size of each download/upload request will not reduce overall bandwidth consumption. Because reducing the size will send more download/upload requests. The overall result will not be much different.
speedtest-go/speedtest/request.go
Line 96 in 856e6e6
It appears that
server.DownloadTest
andserver.UploadTest
use a hard coded image size (which essentially drives the bandwidth impact of these tests) to dlSizes[3] and ulSizes[3].speedtest-go/speedtest/request.go
Lines 20 to 23 in 856e6e6
I am using the GO API to write a simple program that periodically runs speedtest on a regular basis. I'd like to reduce the size of each download/upload test to reduce overall bandwidth consumption since it will be run on an ongoing basis. Recognizing the is likely a tradeoff between test size/bandwith impact and accuracy, but it would be great if the developer could evaluate that tradeoff rather than rely on the hardcoded values currently provided.
The text was updated successfully, but these errors were encountered: