gnmyt
[Bug] Automated speed tests are reporting slower speeds than manual speed tests
General
- [X] I have updated to the latest version of MySpeed.
- [X] My bug has not been reported yet.
The Bug
When running the tests manually using the "start speedtest" button top right, I am getting expected speeds from my ISP. But when an automated test runs the speeds are far lower.
In the provided image, the test at the top is the automated hourly test, and the two below are ones i have ran manually. My instance is running in a proxmox LXC with 1 core and 512mb of ram
What device are you using to access the page?
In the browser
Which operating system is your MySpeed instance running on?
Linux
+1, I'm using the germannewsmaker/myspeed docker image with lxc and proxmox.
Maybe this line? https://github.com/gnmyt/myspeed/blob/0f2248b8b72bd9a26921099056c50246e63f2a31/server/tasks/speedtest.js#L57
Seems to be fixed like this:
speedtest = await speedTest(mode, serverId);
@xhemals this is due to the influx of speed tests at the top of the hour, so the servers are slammed. Go into the storage.db and edit it via whatever SQLite tool you prefer and change the cron value under the config table to something like: 52 * * * *. Then restart your container. This will force the speedtest to run at 52 minutes past the hour, rather than on the hour.
EDIT: You can also do this by going to Settings > Manage Storage > Configuration > Export, modify the cron value, then click the import button and overwrite the config values.
My 2 cents, this app should introduce the ability to set a time manually each hour manually, or set a random time to run them per hour for the above reason of things being slammed on the hour.
This is the same issue I was experiencing. There could be a setting that starts the tests every hour from the time it's enabled for the first time, not at the top of the hour.
@TEBandCo @ekalp You have been able to set a custom cron schedule since release 1.04 #bf48a6c Settings > Set frequency > Set Manually
I have this same problem no matter what I have the frequency set to.
Just to update, i changed my frequency to a random time past the hour as suggested by @ekalp and that seems to have fixed it !
i used the set manually option as per @rtuszik instructions