starred/qBittorrent

Fork 0

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

Global speed limits don't work #3961

New issue

Closed

opened 2026-02-21 17:03:30 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 17:03:30 -05:00

Owner

Originally created by @TehGerg on GitHub (Feb 23, 2016).

I moved to qBittorrent today after Vuze destroyed settings unrelated to it and tried to shoehorn adware onto my computer. A bit of research showed that dBittorrent has a lot of customizable settings and works at considerable speed. I've been happy with it so far.

One issue has arisen though. The global upload and download speed limits don't really seem to affect anything. With uploads supposedly capped at 30, I was getting over 80. With downloads limited supposedly to 500, I was getting closer to 800. Both changes worked for a minute or so and were ignored after that. This happened with manual speed changes or using the alternate speed limits.

There are far worse problems than a bittorrent client working too fast, but there are 6 internet-connected devices in my house, and I can't let dBit hog all the bandwidth at times.

I use OS X 10.11.3 on an iMac with a good processor and plenty of RAM. dBit's version is 3.3.3

Originally created by @TehGerg on GitHub (Feb 23, 2016). I moved to qBittorrent today after Vuze destroyed settings unrelated to it and tried to shoehorn adware onto my computer. A bit of research showed that dBittorrent has a lot of customizable settings and works at considerable speed. I've been happy with it so far. One issue has arisen though. The global upload and download speed limits don't really seem to affect anything. With uploads supposedly capped at 30, I was getting over 80. With downloads limited supposedly to 500, I was getting closer to 800. Both changes worked for a minute or so and were ignored after that. This happened with manual speed changes or using the alternate speed limits. There are far worse problems than a bittorrent client working too fast, but there are 6 internet-connected devices in my house, and I can't let dBit hog all the bandwidth at times. I use OS X 10.11.3 on an iMac with a good processor and plenty of RAM. dBit's version is 3.3.3

deekerman closed this issue

2026-02-21 17:03:32 -05:00

deekerman commented

2026-02-21 17:03:33 -05:00

Author

Owner

@TehGerg commented on GitHub (Mar 6, 2016):

Found the problem. In the Options (Preferences), on the Speed panel, I had checked to enable the µTP protocol, but had not checked to apply the speed limits to µTP. It now works as needed.

I do have to wonder why "global" speed limits would not automatically be applied globally. It seems as if it would make more sense to apply it by default when selecting µTP and then give the option do uncheck it if needed.

@TehGerg commented on GitHub (Mar 6, 2016): Found the problem. In the Options (Preferences), on the Speed panel, I had checked to enable the µTP protocol, but had not checked to apply the speed limits to µTP. It now works as needed. I do have to wonder why "global" speed limits would not automatically be applied globally. It seems as if it would make more sense to apply it by default when selecting µTP and then give the option do uncheck it if needed.

deekerman commented

2026-02-21 17:03:33 -05:00

Author

Owner

@bhrgunatha commented on GitHub (Jun 17, 2017):

I have set the rate limits for utP but I still have NO limit of bandwidth whatsoever - whether global or alternative: I do not schedule these I just switch from global to alternative from time to time but it no longer works. Previous version did work.

Status bar indicator
Torrent status
My Speed Settings

It's been like this since at least 3.3.11 but the arch package was out of date so I've waited to mention it nutil I could update.

Arch 64 bit: - All packages are up to date
qbittorent : 3.3.13 (64 bit)

@bhrgunatha commented on GitHub (Jun 17, 2017): I **have** set the rate limits for utP but I still have **NO** limit of bandwidth whatsoever - whether global or alternative: I do not schedule these I just switch from global to alternative from time to time but it no longer works. Previous version did work. [Status bar indicator](http://i.imgur.com/GMNLQpY.png) [Torrent status](https://i.imgur.com/mly4vFn.png) [My Speed Settings](http://i.imgur.com/wyUihLk.png) It's been like this since at least 3.3.11 but the arch package was out of date so I've waited to mention it nutil I could update. Arch 64 bit: - All packages are up to date qbittorent : 3.3.13 (64 bit)

deekerman commented

2026-02-21 17:03:33 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jun 19, 2017):

2 things to try:
1.Apply rate limit to peers on LAN
2.Change which network adapter qBT is binding to.

@Seeker2 commented on GitHub (Jun 19, 2017): 2 things to try: 1.Apply rate limit to peers on LAN 2.Change which network adapter qBT is binding to.

deekerman commented

2026-02-21 17:03:34 -05:00

Author

Owner

@bhrgunatha commented on GitHub (Jun 19, 2017):

Thanks for the suggestions:

My computer is linked directly to a modem so I see 2 interfaces listed - one for the card (eno1 and one for the modem (ppp0)

I tried all 4 configurations: rate limit on/off and binding to the eno1 and ppp0
Neither of them resulted in any limiting. I also tried with Any interface selected (as it was originally) but that didn't work either.

About versions: It was 3.3.11 when I first noticed the limit failing and previous version did work, but I can't reinstall older version any more.

@bhrgunatha commented on GitHub (Jun 19, 2017): Thanks for the suggestions: My computer is linked directly to a modem so I see 2 interfaces listed - one for the card (eno1 and one for the modem (ppp0) I tried all 4 configurations: rate limit on/off and binding to the eno1 and ppp0 Neither of them resulted in any limiting. I also tried with Any interface selected (as it was originally) but that didn't work either. About versions: It was 3.3.11 when I first noticed the limit failing and previous version did work, but I can't reinstall older version any more.

deekerman commented

2026-02-21 17:03:34 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jun 20, 2017):

Download rate limit nobody has total control over -- if peers and seeds want to "fire-hose" your connection, you're hosed. The limit there is only a suggestion and a pretty mild one at that. After all, if you have 60+ connected seeds -- which one or ones do you tell to slow down a little bit when they go over in total? And if a couple slow down and others speed up to fill in the gaps, nothing changes.

Does the rate limit work for uploads?

@Seeker2 commented on GitHub (Jun 20, 2017): Download rate limit nobody has total control over -- if peers and seeds want to "fire-hose" your connection, you're hosed. The limit there is only a suggestion and a pretty mild one at that. After all, if you have 60+ connected seeds -- which one or ones do you tell to slow down a little bit when they go over in total? And if a couple slow down and others speed up to fill in the gaps, nothing changes. Does the rate limit work for uploads?

deekerman commented

2026-02-21 17:03:34 -05:00

Author

Owner

@bhrgunatha commented on GitHub (Jun 20, 2017):

I haven't been able to check upload limits - it's extremely difficult to find peers to grab seeding torrents and try to max my uploads. And honestly I'm not concerned about that..

I take your point about it being a suggestion, but it used to work!.
I've had time to experiment further and I've managed to downgrade qbittorrent to a version that does limit download rates given the rest of my system configuration .

qbittorent-3.3.9 - Arch package version - qbittorrent-3.3.9-1
libtorrent-rasterbar.so.9.0.0 - Arch package version - libtorrent-rasterbar-1:1.1.1-4
libboost_system.so.1.62.0 - Arch package version - boost-libs-1.62.0-4

But I don't want to use out of date packages - because arch partial upgrades aren't supported, and who knows what security improvements have been made to those libraries and packages.

@bhrgunatha commented on GitHub (Jun 20, 2017): I haven't been able to check upload limits - it's _extremely_ difficult to find peers to grab seeding torrents and try to max my uploads. And honestly I'm not concerned about that.. I take your point about it being a suggestion, but **it used to work!**. I've had time to experiment further and I've managed to downgrade qbittorrent to a version that **does limit** download rates given the rest of my system configuration . * qbittorent-3.3.9 - Arch package version - qbittorrent-3.3.9-1 * libtorrent-rasterbar.so.9.0.0 - Arch package version - libtorrent-rasterbar-1:1.1.1-4 * libboost_system.so.1.62.0 - Arch package version - boost-libs-1.62.0-4 But I don't want to use out of date packages - because arch partial upgrades aren't supported, and who knows what security improvements have been made to those libraries and packages.

deekerman commented

2026-02-21 17:03:34 -05:00

Author

Owner

@Seeker2 commented on GitHub (Jun 20, 2017):

I asked about upload limiting because if that's broken also, it probably means a different bug than just download limiting being broken.

It may be the case that qBT got corrupted somehow -- reinstalling the latest version from scratch (deleting the settings files) might also work.

@Seeker2 commented on GitHub (Jun 20, 2017): I asked about upload limiting because if that's broken also, it probably means a different bug than just download limiting being broken. It may be the case that qBT got corrupted somehow -- reinstalling the latest version from scratch (deleting the settings files) might also work.

deekerman commented

2026-02-21 17:03:34 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang commented on GitHub (Sep 16, 2018): We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0). Please, update to last release and, if the bug/error/crash is still present, open another issue. Thank you.