Description
After renewing the expire TLS certificate (#767), the server list changed. I can't specify precisely, how it was before, but probably it has currently the https schema in all URLs. It causes a strange and unwanted behavior. If librespeed-cli is used on older devices with lower CPU power, it utilizes the CPU(s) up to 100 % due to the encryption and it leads to wrong measurement results (e.g., 55 Mb/s instead of 900 Mb/s).
The actual measurement errors depend to ciphers used on various server. More CPU-intensive ciphers affect the results more.
Server
Not applicable
Client
librespeed-cli 1.0.12
Steps to reproduce
- Run
librespeed-cli --list
- Choose a server (N).
- Run
librespeed-cli --server=<N>
This must be performed on an older device with a slower CPU, such as Turris Omnia (as we observed).
Expected behaviour
The measured speeds should be according to the real situation.
Actual behaviour
The measured speeds are much lower for some servers.
Screenshots
# librespeed-cli --server 85
Retrieving server list from https://librespeed.org/backend-servers/servers.php
Selected server: Prague, Czech Republic (Turris) [librespeed.turris.cz]
Sponsored by: Turris @ https://www.turris.com
You're testing from: 2001:1488:fffe:6260:da58:d7ff:fe00:2152 - CZ.NIC, z.s.p.o., Czechia
Ping: 1.00 ms Jitter: 0.00 ms
Download rate: 56.34 Mbps
Upload rate: 56.19 Mbps
After a temporary fix (redirection from https to http):
# librespeed-cli --server 85
Retrieving server list from https://librespeed.org/backend-servers/servers.php
Selected server: Prague, Czech Republic (Turris) [librespeed.turris.cz]
Sponsored by: Turris @ https://www.turris.com
You're testing from: 2001:1488:fffe:6260:da58:d7ff:fe00:2152 - CZ.NIC, z.s.p.o., Czechia
Ping: 2.00 ms Jitter: 0.00 ms
Download rate: 923.62 Mbps
Upload rate: 727.44 Mbps
Description
After renewing the expire TLS certificate (#767), the server list changed. I can't specify precisely, how it was before, but probably it has currently the https schema in all URLs. It causes a strange and unwanted behavior. If
librespeed-cliis used on older devices with lower CPU power, it utilizes the CPU(s) up to 100 % due to the encryption and it leads to wrong measurement results (e.g., 55 Mb/s instead of 900 Mb/s).The actual measurement errors depend to ciphers used on various server. More CPU-intensive ciphers affect the results more.
Server
Not applicable
Client
librespeed-cli 1.0.12
Steps to reproduce
librespeed-cli --listlibrespeed-cli --server=<N>This must be performed on an older device with a slower CPU, such as Turris Omnia (as we observed).
Expected behaviour
The measured speeds should be according to the real situation.
Actual behaviour
The measured speeds are much lower for some servers.
Screenshots
After a temporary fix (redirection from https to http):