On an ADSL line, high overestimation of upload speed (and little underestimation of download speed)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- cli, networking
Research direction
Start by reproducing the upload and download measurements from speedtest-cli on the stated 7 Mbps/1 Mbps ADSL line, using the Roma and Frankfurt servers and comparing LibreSpeed results. Trace the CLI's upload and download measurement paths; done means the reported upload no longer exceeds the line's actual capacity and download results are consistent with the comparison tests.
Written by the indexing model from the issue text.
Description
Hi,
using speedtest-cli on Windows 10 to test a 7Mbps/1Mbps ADSL line, reporting approximately average results from various test at the same conditions.
With Roma (GARR) server,
where Librespeed web report 6.80 Mbps of download and 0.77 Mbps of upload,
speedtest-cli report a lower 6.20 Mbps of download and report an higher, physically impossible, 1.30 Mbps of upload.
With Frankfurt (Clouvider) server,
where Libre Librespeed web report 7.02 Mbps of download and 0.75 Mbps of upload,
speedtest-cli report a lower 6.35 Mbps of download and report an higher, physically impossible, 2.80 Mbps of upload.
Speedtest.net (using uBlock to remove ads) with various server in Roma,
reports an average 6.50 Mbps of download and an average 0.75 Mbps of upload.
Speedtest.net (using uBlock to remove ads) with Frankfurt (Clouvider) server, the same of Librespeed,
reports an average 6.57 Mbps of download and an average 0.75 Mbps of upload.
It seems that in my case, speedtest-cli:
- reports a much higher value of upload (physically impossible) than the actual value
- reports a slightly lower value of download, than the actual value
- Dominant language
- Go
- Stars
- 845
- Forks
- 90
- Avg merge
- 11d 22h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from librespeed/speedtest-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
librespeed/speedtest-cli#121 ·
-
Add /api endpoint Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
librespeed/speedtest-cli#151 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
librespeed/speedtest-cli#120 · 2 comments · 1 reaction ·
-
Host image in ghcr Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
librespeed/speedtest-cli#118 · 5 comments · 4 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
librespeed/speedtest-cli#114 · 4 comments ·
All issues in librespeed/speedtest-cli
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100