Skip to content
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

[Bug] Automated speed tests are reporting slower speeds than manual speed tests #902

Open
2 tasks done
xhemals opened this issue Nov 23, 2024 · 3 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@xhemals
Copy link

xhemals commented Nov 23, 2024

General

  • I have updated to the latest version of MySpeed.
  • 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.

image

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

@xhemals xhemals added the bug Something isn't working label Nov 23, 2024
@muuuh
Copy link

muuuh commented Nov 28, 2024

+1, I'm using the germannewsmaker/myspeed docker image with lxc and proxmox.

Maybe this line?

speedtest = await (retryAuto ? speedTest(mode) : speedTest(mode, serverId));

Seems to be fixed like this:

        speedtest = await speedTest(mode, serverId);

@ekalp
Copy link

ekalp commented Dec 16, 2024

@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.

@TEBandCo
Copy link

TEBandCo commented Feb 2, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants