starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

dl/ul speed discrepancies (or impossible speeds) in status bar, title bar vs. speeds shown in transfer list #8777

New issue

Open

opened 2026-02-21 19:48:22 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 19:48:22 -05:00

Owner

Originally created by @Aniverse on GitHub (Jun 5, 2019).

Please provide the following information

qBittorrent version and Operating System

4.1.5 or 4.1.6, Ubuntu 16.04/18.04 or Debian 8/9

If on linux, libtorrent and Qt version

libtorrent 1.1.12 or 1.1.13
Qt 5.5.1 or 5.7.1 or 5.9.5

What is the problem

I'm a seedbox user and I'm using qbittorrent-nox. I'm using a 1Gbps HDD seedbox.

Obviously this is impossible for a 1Gbps seedbox with only HDD as storage. Such siuation occurs many times but this is the most ridiculous one.

And the sum of the speeds of single torrents is also very different from the speed shown in status bar, when sum of single torrents' upload speed is 30MiB/s, the speed shown in status bar maybe 70MiB/s, that would make me confused, as I'm not sure which speed is the actual speed.

I have read #8738, but it can't explain 4.73GiB/s on 1Gbps server.

What is the expected behavior

Normal speed display, and what about to make the speed shown is status bar be the same as sum of single torrents' speed? (I know the speed in status bar includes payload, but this will confuse many users)

Steps to reproduce

Add some torrents and start them.

Extra info(if any)

It seems this bug only occurs on qbt 4.x (tbh I'm not sure if this occurs on qbt 4.0 but on qbt 4.1.x this bug do exist), when I was using qbt 3.3.x I have never had such a problem.
This is a very common issue as I know (see also #9946, #8847), and many other seedbox qbittorrent-nox users had reported me the same issue and then they stuck to using qbt 3.3.11.

Originally created by @Aniverse on GitHub (Jun 5, 2019). **Please provide the following information** ### qBittorrent version and Operating System 4.1.5 or 4.1.6, Ubuntu 16.04/18.04 or Debian 8/9 ### If on linux, libtorrent and Qt version libtorrent 1.1.12 or 1.1.13 Qt 5.5.1 or 5.7.1 or 5.9.5 ### What is the problem I'm a seedbox user and I'm using qbittorrent-nox. I'm using a 1Gbps HDD seedbox. ![speed](https://user-images.githubusercontent.com/25970160/58966344-b9bd6080-87e4-11e9-8a1f-b354cc596893.png) Obviously this is impossible for a 1Gbps seedbox with only HDD as storage. Such siuation occurs many times but this is the most ridiculous one. And the sum of the speeds of single torrents is also very different from the speed shown in status bar, when sum of single torrents' upload speed is 30MiB/s, the speed shown in status bar maybe 70MiB/s, that would make me confused, as I'm not sure which speed is the actual speed. I have read #8738, but it can't explain 4.73GiB/s on 1Gbps server. ### What is the expected behavior Normal speed display, and what about to make the speed shown is status bar be the same as sum of single torrents' speed? (I know the speed in status bar includes payload, but this will confuse many users) ### Steps to reproduce Add some torrents and start them. ### Extra info(if any) It seems this bug only occurs on qbt 4.x (tbh I'm not sure if this occurs on qbt 4.0 but on qbt 4.1.x this bug do exist), when I was using qbt 3.3.x I have never had such a problem. This is a very common issue as I know (see also #9946, #8847), and many other seedbox qbittorrent-nox users had reported me the same issue and then they stuck to using qbt 3.3.11.

deekerman added the

Confirmed bug

Core

GUI

labels

2026-02-21 19:48:22 -05:00

deekerman commented

2026-02-21 19:48:24 -05:00

Author

Owner

@geekcdy commented on GitHub (Jun 29, 2019):

Same issue here

@geekcdy commented on GitHub (Jun 29, 2019): Same issue here

deekerman commented

2026-02-21 19:48:26 -05:00

Author

Owner

@yezi1000 commented on GitHub (Jul 23, 2019):

Same problem

@yezi1000 commented on GitHub (Jul 23, 2019): Same problem ![photo_2019-07-23_14-21-27](https://user-images.githubusercontent.com/30385445/61687547-413f3e80-ad55-11e9-8acb-7f73a80295dc.jpg)

deekerman commented

2026-02-21 19:48:26 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Mar 11, 2020):

~~Duplicate of https://github.com/qbittorrent/qBittorrent/issues/7920~~

@FranciscoPombal commented on GitHub (Mar 11, 2020): ~Duplicate of https://github.com/qbittorrent/qBittorrent/issues/7920~

deekerman commented

2026-02-21 19:48:26 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Aug 7, 2020):

Apologies for erroneously marking this as a duplicate of the "impossible speed in graphs" bug, which is now fixed.

I can confirm this one, as I've recently observed this on an Ubuntu 18.04 system with a very active torrent that was saturating both my uplink and downlink. The system was also under quite high I/O contention, which might play a role in this. Speed values in the title/status bar were fluctuating wildly between several dozen MiB/s and dozens/hundreds of KiB/s, and varied wildly from the smoother range of values shown in the transfer list and graph, which seemed to be more in line with the actual download progress. Additionally, I'm pretty sure at times some of the download speed values displayed in the status/title bar were actually impossible.

qBittorrent version used: 4d1c5a8aea (most recent master commit at time of writing) + libtorrent 1.2.8 (release tag)

@FranciscoPombal commented on GitHub (Aug 7, 2020): Apologies for erroneously marking this as a duplicate of the "impossible speed in graphs" bug, which is now fixed. I can confirm this one, as I've recently observed this on an Ubuntu 18.04 system with a very active torrent that was saturating both my uplink and downlink. The system was also under quite high I/O contention, which might play a role in this. Speed values in the title/status bar were fluctuating wildly between several dozen MiB/s and dozens/hundreds of KiB/s, and varied wildly from the smoother range of values shown in the transfer list and graph, which seemed to be more in line with the actual download progress. Additionally, I'm pretty sure at times some of the download speed values displayed in the status/title bar were actually impossible. qBittorrent version used: 4d1c5a8aea9fc2a5d46a16c7f23a39733cfaad20 (most recent master commit at time of writing) + libtorrent 1.2.8 (release tag)

deekerman commented

2026-02-21 19:48:26 -05:00

Author

Owner

@Marko-HR commented on GitHub (Dec 6, 2020):

Apologies for erroneously marking this as a duplicate of the "impossible speed in graphs" bug, which is now fixed.

I can confirm this one, as I've recently observed this on an Ubuntu 18.04 system with a very active torrent that was saturating both my uplink and downlink. The system was also under quite high I/O contention, which might play a role in this. Speed values in the title/status bar were fluctuating wildly between several dozen MiB/s and dozens/hundreds of KiB/s, and varied wildly from the smoother range of values shown in the transfer list and graph, which seemed to be more in line with the actual download progress. Additionally, I'm pretty sure at times some of the download speed values displayed in the status/title bar were actually impossible.

qBittorrent version used: 4d1c5a8 (most recent master commit at time of writing) + libtorrent 1.2.8 (release tag)

Any news regarding this? When could this potentially be fixed?

@Marko-HR commented on GitHub (Dec 6, 2020): > Apologies for erroneously marking this as a duplicate of the "impossible speed in graphs" bug, which is now fixed. > > I can confirm this one, as I've recently observed this on an Ubuntu 18.04 system with a very active torrent that was saturating both my uplink and downlink. The system was also under quite high I/O contention, which might play a role in this. Speed values in the title/status bar were fluctuating wildly between several dozen MiB/s and dozens/hundreds of KiB/s, and varied wildly from the smoother range of values shown in the transfer list and graph, which seemed to be more in line with the actual download progress. Additionally, I'm pretty sure at times some of the download speed values displayed in the status/title bar were actually impossible. > > qBittorrent version used: [4d1c5a8](https://github.com/qbittorrent/qBittorrent/commit/4d1c5a8aea9fc2a5d46a16c7f23a39733cfaad20) (most recent master commit at time of writing) + libtorrent 1.2.8 (release tag) Any news regarding this? When could this potentially be fixed?