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

Known issue: Poor speedtest/networking performance in WSL (maybe macOS) #139

Closed
alexjustesen opened this issue Nov 10, 2022 · 0 comments
Closed
Assignees
Labels
🐛 bug Something isn't working

Comments

@alexjustesen
Copy link
Owner

alexjustesen commented Nov 10, 2022

Problem statement

On certain host systems speedtests can differ drastically between running the test from the host OS and from within the Speedtest Tracker container.

Warning
If you use speedtest.net browser results to quantify the issue I'll throw out the results, you've been warned.

Warning
If you're testing this over wifi, LOL

Windows Subsystem for Linux (WSL)

Status: ✅ confirmed
Fix: ⬜ tbd

Steps to reproduce

  1. Select a server and make sure you're testing against the same server each time
  2. Run a speedtest from within the Speedtest Tracker UI
  3. Run a speedtest from within the Speedtest Tracker Docker container with the command speedtest --server-id=#####
  4. Install the Speedtest CLI in WSL (using the Ubuntu/Debian steps) and run the speedtest from WSL with the command speedtest --server-id=#####`
  5. If your results differ from a health margin (say more than 20%) you're likely having this issue.

MacOS

Status: ⬜ unconfirmed
Fix: ⬜ tbd

Steps to reproduce

  1. Select a server and make sure you're testing against the same server each time
  2. Run a speedtest from within the Speedtest Tracker UI
  3. Run a speedtest from within the Speedtest Tracker Docker container with the command speedtest --server-id=#####
  4. Install the Speedtest CLI in WSL (using the macOS steps) and run the speedtest from WSL with the command speedtest --server-id=#####`
  5. If your results differ from a health margin (say more than 20%) you're likely having this issue.

Debugging

Before saying "me too" please follow the debugging steps below, I'll be adding more as I learn more about the issue and as possibilities are ruled out.

Check your network card

Make sure your hardware actually supports the networking speed you'd expect to see, @JohnnyDeeee gave some tips here #126 (comment).

Don't test the container and then run a speedtest on speedtest.net

These fundamentally don't use the same networking protocol and introduce more variables into the testing process to uncover the root cause. To accurately identify and test against this issue follow the "steps to reproduce under your OS".

Links

Research

Related issues from this project

@alexjustesen alexjustesen added the 🐛 bug Something isn't working label Nov 10, 2022
@alexjustesen alexjustesen self-assigned this Nov 10, 2022
@alexjustesen alexjustesen pinned this issue Nov 10, 2022
@alexjustesen alexjustesen changed the title Known issue: Poor speedtest/networking performance on Windows WSL Known issue: Poor speedtest/networking performance in WSL (maybe macOS) Nov 10, 2022
@alexjustesen alexjustesen unpinned this issue Jan 29, 2023
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

1 participant