I’ve updated to cu 198 just after release and noticed quite quickly, that my “automatic internet check” using speedtest dropped to 50%. However, when checking in the browser using both speedtest.net and fast.com didn’t show any problems, but downloading bigger files did. Funny enough, when downloading a file (with ~50% speed) and checking the speed using a browser it in combination also showed me the full speed.
This happened immediately after updating, here you can see how it dropped and it stayed like this since:
I don’t have any QoS activated, so everything should get the same speed. The most surprise I have, is that browser based testing shows the same speed, but CLI or downloads are slower. There haven’t been any other changes to the IPFire configuration or hardware, that would explain this dropped…
Do you have any glue or hint, where this might come from?
TL;DR: Internet connection speed dropped to 50% for downloads and CLI, but browser testing using like speedtest shows still 100% of the speed.
And anyway.. it’s possible to have reported more data on your setup (mainboard, cpu, network cards or device brand and model)
According to this post
the latest kernel is based on Linux 6.12.41 and CU 198 did not mentioned any kernel change, so at least by drivers everything should be the same… Was CU197 skipped?
CU198 introduces newer intel Microcodes, which could deliver some performance drawbacks (mostly of the times under 10%…)
Thanks for your replies. I’m having this setup running for many years already and usually I’m installing the latest core updates quite quickly, over the years I maybe missed only a couple, so yes, cu 197 has been installed and as promised I saw a big drop in CPU usage, but not in internet speed.
The hardware I’m using is a PC Engine APU2, which is running with an “AMD GX-412TC SOC” 4 core CPU and 4GB Memory. Network wise it has three NICs, but I can’t tell from heart, which are those. I try to find the exact APU model later.
It’s using the latest kernel, so that is “6.12.41-ipfire” and the latest available firmware (4.19.0.1-16).
I’ve just tested it again, but the CPU usage is jumping to ~40% max when running speedtest multiple times, therefore I can’t imagine, that there is a real hardware issue. But true, the board and CPU are pretty old, so there might have been a microcode update, that causes this issue.
Well, this is my home setup, so rolling back would be quite an act, I’ve also never done it though and the installation is a couple of years in the past… But yes, that would be an option…
I actually run it behind an Vigor167, so no CPE included. This is also running for a couple of months now (since my FritzBox died) and there wasn’t any change I know. The Vigor also shows the same DSL information as before (yes, not the best line, but that’s what I have…):
The thing that is strange to me, I had a line degradation in the past, but that was only around ~15% and I could see it in the FritzBox DSL stats (at that time). This time, it is only visible when having actual downloads or using the speedtest-cli, but not on browser side (or using speedtest in the browser). As I said, when I’m downloading something and starting speedtest in the browser, the IPFire UI shows the full speed used in the UI, but when the test in the browser is done it falls back to ~50%. So I can’t imagine a line degredation here and from the past I know, that the ISP will ask me to do a speedtest in the browser…
Good point, I’ve just tested it again making sure, to use the same server and also used the “–secure” flag. The picture is the same:
Selecting best server based on ping…
Hosted by Net-D-Sign GmbH (Munich) [0 km]: 20.915 ms
Testing download speed…
Download: 44.65 Mbit/s
Testing upload speed…
Upload: 35.66 Mbit/s
The author of speedtest-cli posted the following information on his GitHub page:
It is not a goal of this application to be a reliable latency reporting tool.
Latency reported by this tool should not be relied on as a value indicative of ICMP style latency. It is a relative value used for determining the lowest latency server for performing the actual speed test against.
There is the potential for this tool to report results inconsistent with Speedtest.net. There are several concepts to be aware of that factor into the potential inconsistency:
Speedtest.net has migrated to using pure socket tests instead of HTTP based tests
1.This application is written in Python
2.Different versions of Python will execute certain parts of the code faster than others
3.CPU and Memory capacity and speed will play a large part in inconsistency between Speedtest.net and even other machines on the same network
Issues relating to inconsistencies will be closed as wontfix and without additional reason or context.
edit
The official Ookla speedtest CLI command line client is available on the following page.