Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

obviously impossible dl/ul speed shown in status bar #10766

Aniverse opened this issue Jun 5, 2019 · 0 comments


None yet
1 participant
Copy link

commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.