Results are very different from what Speedtest.com shows

[BornInTheUSA]

Screenshot from Speedtest-Tracker

Screenshot from Speedtest.com

[alexdelprete]

Is the selected server the same? Try specifying the same server if you want to compare results.

[BornInTheUSA]

Selecting the same server on Speedtest.com shows even larger differences.

[alexdelprete]

Did you set the same serverid in speedtest-tracker? Can you show the screenshot of both speedtes-tracker AND speedtest web site with server-id visible? I only see speeds here, can't compare anything.

What platform are you on? Describe the environment a little bit...thanks.

[BornInTheUSA]

Screenshots of of server id's.
![Screen Shot 2022-11-05 at 4 48 50 PM](https://user-images.githubusercontent.com/53592632/200142659-522c9e2e-a19a-4b85-a39f-b18e

54ffe5a8.png)

This is on a Mac Pro Mid 2012

[BornInTheUSA]

[alexdelprete]

Can you do the test on mac's shell with speedtest-cli from ookla?

Install instructions:

brew tap teamookla/speedtest
brew update
brew install speedtest --force

Then you use this command to specify the server id (12190 is the one you used in speedtest-tracker):

speedtest -s 12190

And post the results, thanks.

[BornInTheUSA]

[alexdelprete]

speedtest --server 12190

[BornInTheUSA]

[BornInTheUSA]

Fixed OOla cli

[alexdelprete]

And you have 12190 in the Speedtest server field in Settings->General, right?

If so...that is really strange. You're using latest version of speedtest-tracker (v0.2.0), right?

[BornInTheUSA]

The latest version for MAC is 1.2.0.84. That is what was installed from brew.

[alexdelprete]

I was referring to speedtest-tracker, this project, not speedtest-cli. :)

[BornInTheUSA]

I just redeployed from this repo and same results.

[alexdelprete]

how are you deploying, docker-compose? can you show me the docker-compose.yml file? thanks.

[BornInTheUSA]

version: '3.3'
services:
speedtest-tracker:
container_name: speedtest-tracker
ports:
- '8443:443'
environment:
- PUID=1000
- PGID=1000
- DB_CONNECTION=mysql
- DB_HOST=db
- DB_PORT=3306
- DB_DATABASE=speedtest_tracker
- DB_USERNAME=speedy
- DB_PASSWORD=password
volumes:
- '/Users/rmartin/Docker/config:/config'
image: 'ghcr.io/alexjustesen/speedtest-tracker:latest'
depends_on:
- db
db:
image: mariadb:10
restart: always
environment:
- MARIADB_DATABASE=speedtest_tracker
- MARIADB_USER=speedy
- MARIADB_PASSWORD=password
- MARIADB_RANDOM_ROOT_PASSWORD=true
volumes:
- speedtest-db:/var/lib/mysql
volumes:
speedtest-db:

[alexdelprete]

ok, you used tag latest, so it should be 0.2.0. In the UI I think there's no indication of the version, it should be added somewhere.

I don't know what to advice, sorry, on my installation the speed results are in line to what I observe with speedtest-cli. I hope @alexjustesen can help you more than I could.

[JohnnyDeeee]

I had the same problem, so i tried running speedtest inside the speedtest-tracker docker container, which showed the same problem (~ 100mbps)

I then ran the same speedtest on my host machine (Intel NUC10) which showed the same low speeds!
After a couple hours searching i found out that this machine somehow doesn't use the right Advertised speed on it's network card. You can check what speed it is at by running

ethtool <your network interface>

To get the network interface run ifconfig and check which one has your local IP address.

Mine showed a speed of 100, but the Supported link modes showed

Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full

Edit: Don't follow my steps below, a better way of fixing this is upgrading your kernel so you get the latest patches

So i looked around and found this command

ethtool -s <your network interface> advertise 0x1800000001028

which should "fix" the wrong advertised speeds. When i run this i got 1000Mb/s as my speed.

This change is not permanent though. If you reboot the change is gone..
In Ubuntu 22.04 i had to create the following file

/etc/networkd-dispatcher/configured.d/<whatever you want to call it, i used my interface name here>

and put this inside

#!/bin/sh
ethtool -s eno1 advertise 0x1800000001028 || true

i then restarted my machine and noticed that my speeds were still at 1000Mb/s

You probably don't have the exact same setup but i hope this will point you in a direction.

[BornInTheUSA]

I used ifconfig command and the connection speed is advertised as 1 Gbit/s

[alexdelprete]

You probably don't have the exact same setup but i hope this will point you in a direction.

he observed values well above 100Mb/s, so that could not be his specific issue.

[JohnnyDeeee]

I used ifconfig command and the connection speed is advertised as 1 Gbit/s

Is this the same machine that runs speedtest-tracker?

he observed values well above 100Mb/s, so that could not be his specific issue.

Oops, totally missed that!

[psyko-gh]

For the records, I have the same issue:

• Setup: Docker using the latest image
• Server configured to use the suggested one by speedtest.net
• Speedtest-tracker results:
  Down: 260Mbps Up: 375Mbps Ping: 11ms
• Speedtest app (for Windows)
  Down: 860 Mbps Up: 540 Mbps Ping: 10ms

So ping is consistent, but speeds are not..
Both ran on the machine hosting the docker container.
I tried with other servers ids and the results vary the same way.

Let me know if you need more information

Edit: It looks like Docker for windows may have some performance issues ?
docker/for-win#698
Didn't went through the whole issue, but I'll have to take a look at that

[alexdelprete]

It looks like Docker for windows may have some performance issues ? I'll have to dig into that.

@BornInTheUSA is using a Mac, so I would exclude that it's docker on windows.

[alexjustesen]

It looks like Docker for windows may have some performance issues ? I'll have to dig into that.

@BornInTheUSA is using a Mac, so I would exclude that it's docker on windows.

I also have the issue for Docker on Windows but it's not something I've dug deep into yet as it's likely out of the control of the app.

[alexdelprete]

I also have the issue for Docker on Windows but it's not something I've dug deep into yet as it's likely out of the control of the app.

if you do a speedtest-cli from the inside of the container on windows, the results are different vs the app?

[alexjustesen]

I also have the issue for Docker on Windows but it's not something I've dug deep into yet as it's likely out of the control of the app.

if you do a speedtest-cli from the inside of the container on windows, the results are different vs the app?

by "different" they're slower than they should be for sure

[psyko-gh]

if you do a speedtest-cli from the inside of the container on windows, the results are different vs the app?

A speedtest-cli from the speedtest-tracker docker give the same result as the speedtest-tracker app (3 to 4 times slower than the dedicated speedtest app).
I tried the Get-netadpaterRSC | Disable-netadapterRSC command, but no success

[alexdelprete]

by "different" they're slower than they should be for sure

so inside the container it's slower, and a speedtest from the host side is normal. looks like it's something related to docker, but only on windows and mac...very interesting.

[BornInTheUSA]

On Ubuntu results are correct. And this Ubuntu is running as a VM on my MAC.

[alexdelprete]

On Ubuntu results are correct. And this Ubuntu is running as a VM on my MAC.

Do you have a windows VM to try the same test? Would be interesting to compare.

Also: did you try speedtest-cli from the shell inside the container on mac and ubuntu?

[BornInTheUSA]

Docker will not run on a Windows VM since it requires Windows HyperV or WSL.

[alexdelprete]

Docker will not run on a Windows VM since it requires Windows HyperV or WSL.

https://github.com/StefanScherer/windows-docker-machine

[BornInTheUSA]

I am using Parallels for my VM's and do not feel the need to install https://github.com/StefanScherer/windows-docker-machine
You should just mark speedtest-tracker not for Windows or MACOS

[alexdelprete]

You should just mark speedtest-tracker not for Windows or MACOS

I don't think that is the solution, it's just a way to bypass problems.

Didn't want to force you doing anything, we're trying to understand what the problem is.

Thanks for the help.

[alexjustesen]

Heads up going to track this under a parent issue with specific testing criteria so we can hopefully narrow this down. Closing this issue and moving the convo to #139