Global speed limits ignored

[Spadge]

Speed limits set at 4MB globally, max 4MB per torrent.

When adding one torrent and letting it run, speed is max 4MB on the download.

When adding a second torrent, speed ignores the 4MB global limit and maxes out my connection at 6MB. Each file continues to obey the 4MB per torrent.

​http://forum.deluge-torrent.org/viewtopic.php?f=8&t=54837

[ElectronicWar]

Can confirm, deluged 2.0 ignores the global limit, but obeys the per-torrent limit, see attached screenshot.

My system:

• Debian Stretch 9.3 ((Raspbian arm-hf)
• Latest Deluge 2.0.0.dev7125 via "artful" develop PPA
• Latest libtorrent 1.1.6.0 via "artful" develop PPA
• Python 2.7.13

[booboom]

i will second this motion.

it happened about 2 months ago (december 2017) and if I remember correctly, a rasterbar9 update caused the global limits to not apply. (i did not notice that the update to deluge 2.0.0.7125 caused the global limits to be ignored)

using Linux haarUDOO 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 17.10 artful aardvark

had to switch back to deluge 1.13.15 because i needed the global limits... (i switched back on jan 16.2018... when fixed, will go to deluge 2.0.0.7125)

[graysky]

I believe this extends beyond the 2.0 release. Arch Linux uses the 1.3.x branch and I see the bug on it.

Client and server: 1.3.15 libtorrent: 1.1.6.0

We are building from: ​git://git.deluge-torrent.org/deluge.git#commit=b8e5ebe8220c8365e186127e381a2d2dbaf9e460

This is with a global setting of 250 and a per torrent of -1:

If I change the per torrent to 250, it behaves as expected.

[ElectronicWar]

Replying to graysky:

I believe this extends beyond the 2.0 release. Arch Linux uses the 1.3.x branch and I see the bug on it.

Its a general issue with deluged 1.3 and libtorrent 1.x It only properly supports libtorrent 0.16.x branch.

[Funky_Funked]

I encountered this bug too since a week or so:

Ubuntu 14.04 libtorrent 1.1.6.0 Deluge 1.3.15

Global upload and download limits are ignored completely, per-torrent limits work.

Only thing i can remember i changed on my system was a recent dist-upgrade.

Is there a temporary fix? A fresh Deluge install gives me the exact same problem... Really really annying as i seed a lot of torrents and it completely takes my upload-speed and takes my complete bandwith hostage. :(

Replying to ElectronicWar:

Replying to graysky:

I believe this extends beyond the 2.0 release. Arch Linux uses the 1.3.x branch and I see the bug on it.

Its a general issue with deluged 1.3 and libtorrent 1.x It only properly supports libtorrent 0.16.x branch.

How can i get libtorrent 0.16.x insted of 1.1.6.0? Do i need to build it from source, if so, where do i get it?

[ElectronicWar]

Replying to Funky_Funked:

How can i get libtorrent 0.16.x insted of 1.1.6.0? Do i need to build it from source, if so, where do i get it?

I used a Debian Jessie .deb package for it (and the one or two dependencies of it) and manually installed it and set a apt pin.

[graysky]

A work-around is to set a per-torrent speed limit.

[int3l]

Just for reference- the global limits seems to work on Windows 7 SP1 64 bit and the latest Deluge build in daemon mode:
Client: 1.3.15
Server: 1.3.15
libtorrent: 1.0.11.0

So maybe this is the latest version of libtorrent that Deluge supports properly.

[Funky_Funked]

Ok i got it all working again with python-libtorrent 1.0.11 on Ubuntu 14.04 instead of 1.1.6. Thanks for all the infos.

[djipey]

Bug still present. On Archlinux, the bug is caused by libtorrent-rasterbar-1:1.1.7-2. It's possible to fix it by downgrading it to libtorrent-rasterbar-1:1.1.6-1.

But downgrading libtorrent-rasterbar also downgrades boost-libs. And Libreoffice is not compatible with the downgraded version off boost-libs...

[Spadge]

Appears to have been silently fixed - no mention of it on ​https://github.com/arvidn/libtorrent/issues/2857 but hey, I'm not complaining.

Thanks for picking this up and making the case Cas, you're a star.