Low speed values with selected server in config.yml

[alexdelprete]

I noticed really low speed values reported in the admin panel, I just did a manual test with the server 4302 I configured in config.yml:

speedtest:
  enabled: true
  schedule: '*/40 * * * *' # every hour
  ookla_server_id: 4302 # specify a server ID to use a sepecific server
tz: 'Europe/Rome'

   Speedtest by Ookla

      Server: Vodafone IT - Milan (id: 4302)
         ISP: Tecno General S.r.l
Idle Latency:     8.64 ms   (jitter: 0.31ms, low: 8.36ms, high: 9.29ms)
    Download:   813.10 Mbps (data used: 874.1 MB)
                 42.38 ms   (jitter: 38.70ms, low: 9.66ms, high: 941.40ms)
      Upload:   261.07 Mbps (data used: 150.7 MB)
                  9.76 ms   (jitter: 0.77ms, low: 8.44ms, high: 12.24ms)
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/158c6f1d-3278-4606-b24a-fbd142c6deec

Is alpha.6 still using config.yml? If that's the case, I'm worried about the performance within docker, but the old speedtest-tracker worked fine in that regard. How do I check detailed info of a single test (server used, etc.)?

[alexjustesen]

This might be related to docker networking, can you try running the container on the host network? Looks like an issue was opened on the original repo too henrywhitaker3/Speedtest-Tracker#919 (comment)

[Kostecki]

I'm experiencing this as well. Messing with docker networking doesn't seem to improve anything. Speeds are consistently 8-10 times lower than expected.

I have a container with the original repo running alongside - here i don't have any problems maxing my connection.

[alexdelprete]

This might be related to docker networking, can you try running the container on the host network? Looks like an issue was opened on the original repo too

Tried with host network, made no difference. My suspicion is that it's not using the server I configured, or something related to the version of speedtest-cli, I remember I had this problem on the original project version, shelled in the container and updated speedtest-cli manually, it used a very old version of it, and after the upgrade, speeds were fine.

[alexdelprete]

I have a container with the original repo running alongside - here i don't have any problems maxing my connection.

Yup, same for me. But I remember I had this issue with the old project too, and fixed it upgrading speedtest-cli. Since then, everything was ok.

[alexjustesen]

I've got family in town for a couple of days but I'll look into this ASAP. It's happening for me as well

[alexdelprete]

It's happening for me as well

Glad you have the same issue, so you can trace it. No worries about timing, no emergency.

[Kostecki]

I get the expected results when i run the speedtest directly inside the container. Same server for both tests and the test themselves are run pretty much back to back.

The current version of the speedtest binary (1.2.0.84) also seems to be the latest version available from Ookla, so probably no issues there.

[alexdelprete]

I get the expected results when i run the speedtest directly inside the container. Same server for both tests and the test themselves are run pretty much back to back.

My suspect is that the scheduled tests are not run against the configured server. From the UI there's no column indicating which server ID has been used for each test.

The current version of the speedtest binary (1.2.0.84) also seems to be the latest version available from Ookla, so probably no issues there.

Yes 1.2.0.84 is the latest. Thanks for reporting this, at least we can exclude that problem.

[Kostecki]

My suspect is that the scheduled tests are not run against the configured server. From the UI there's no column indicating which server ID has been used for each test.

There is in the database though (i use MariaDB) and the server_id/server_name columns do match with the value i provided in the config.yml - at least for me.

[alexdelprete]

Thanks. So that's weird...I hope Alex finds the issue.

[alexjustesen]

Next release will contain the server info in the results table #38.

Still working on the speed issue

[alexjustesen]

I've also confirmed speed tests are running slow from within the container, not a clue why just yet but documenting results below...

Internet plan 1gbps/1gbps

CLI from WSL

   Speedtest by Ookla

      Server: Frontier - Wallingford, CT (id: 14235)
         ISP: Frontier Communications
Idle Latency:     5.66 ms   (jitter: 0.54ms, low: 5.03ms, high: 6.41ms)
    Download:   937.26 Mbps (data used: 1.3 GB)
                 11.83 ms   (jitter: 1.23ms, low: 4.36ms, high: 19.07ms)
      Upload:   922.49 Mbps (data used: 497.1 MB)
                  6.97 ms   (jitter: 1.05ms, low: 4.67ms, high: 10.50ms)
 Packet Loss:     0.0%

CLI from within the container

Speedtest by Ookla

      Server: Frontier - Wallingford, CT (id: 14235)
         ISP: Frontier Communications
Idle Latency:     5.77 ms   (jitter: 0.21ms, low: 5.67ms, high: 5.99ms)
    Download:   238.27 Mbps (data used: 212.5 MB)                                                   
                  6.25 ms   (jitter: 1.49ms, low: 4.34ms, high: 15.75ms)
      Upload:   237.21 Mbps (data used: 390.4 MB)                                                   
                  6.26 ms   (jitter: 1.94ms, low: 4.25ms, high: 33.07ms)
 Packet Loss:     0.0%