Slow internet speeds on fedora 40 (wifi and ethernet)

Hello,

I am having an issue with my internet speeds on the new PC with fedora 40. My internet averages out around 50Mbps but some programs (I’ve noticed Steam, qbittorent and Heroic Games Launcher) use up to 6Mbps. (I’ve checked their settings, they’re not limited)

I looked at some similar topics but couldn’t solve it.


On steam it even shows the current speed to be 55Mbps but that clearly isn’t the case as it would not take 2.5 hours to download 50Gb with those speeds.

Results of inxi -z -n command:

Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE driver: r8169
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>

Results of lspci | grep -Ei 'ether|net|wire' command:

00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)

Results of uname -a command:

Linux thebeast 6.9.5-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jun 16 15:47:09 
UTC 2024 x86_64 GNU/Linux

Results of ip a command:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 74:56:3c:b8:68:21 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.26/24 brd 192.168.1.255 scope global dynamic noprefixroute enp4s0
       valid_lft 83563sec preferred_lft 83563sec
    inet6 fe80::bebb:74cc:c3c:447f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether ca:c5:fa:ed:67:f3 brd ff:ff:ff:ff:ff:ff permaddr a0:02:a5:ab:b0:c1
    altname wlp0s20f3

The speed of 50Mbps was done by www.speedtest.net on both other devices and this PC.
I tried turning off wifi or plugging out the ethernet cable and using both at the same time with similar results.

I hope this is enough info for someone to help me fix this :]

Cheers!

Hi,
It seems you’re missing the fact that the download speed is in bits and the file size is in bytes.

how long would it take to download a 100 Gigabyte file at a speed of 55 Mbps (million bits per second)?

To calculate how long it would take to download a 100 Gigabyte (GB) file at a speed of 55 Mbps (megabits per second), you need to convert both the file size and the download speed to the same unit. Since Mbps measures speed in bits, and 1 byte equals 8 bits, converting the file size to megabits (Mb) is necessary.

First, convert the file size from GB to Mb:

  • 100 GB = 100 * 1024 MB (since 1 GB = 1024 MB) = 102,400 MB
  • Convert MB to Mb: 102,400 MB * 8 bits/byte = 819,200 Mb

Next, calculate the download time by dividing the total size of the file in Mb by the download speed in Mbps:

  • Download time = Total file size in Mb / Download speed in Mbps
  • Download time = 819,200 Mb / 55 Mbps = 14,864 seconds

Convert seconds to hours, minutes, and seconds:

  • Hours = 14,864 / 3600 ≈ 4.11 hours
  • Remaining seconds = 14,864 % 3600 = 1360 seconds
  • Minutes = 1360 / 60 ≈ 22.67 minutes
  • Remaining seconds = 1360 % 60 = 40 seconds

Therefore, it would take approximately 4 hours, 22 minutes, and 40 seconds to download a 100 GB file at a speed of 55 Mbps, assuming a constant download speed.

At 48%, just over 2 hours looks normal.

Hope it helps.

1 Like

An additional factor that adds to the time calculated above is the fact that for every single packet of data that is transferred on the internet (or LAN) there are added headers that contain identification, size, packet sequence, packet checksums, routing information, etc. Thus there is usually an additional 10 to 20 percent added overhead in data transfer. A 100 MB file then actually involves about 110+ MB of actual network traffic and not just the size of the data being moved. Those headers are not counted in the size of the data transferred since they are network overhead and not data – though they are part of the bps transfer speed reported.

An added part of that is that sometimes a packet may be corrupted (or lost) and must be sent again – which involves time to communicate from end to end to solve the problem. This also adds to the time required to complete a full transfer as well as causing a larger amount of network traffic for the same size data.

1 Like

Alright, thank you very much.

I suppose I didn’t download such large files in a long time so it felt way to long.

Apologies for misunderstanding this and thanks again for help!

Cheers!

2 Likes