Max global upload rate limit doesn't work correctly

[yodas_brother]

Hi, last night I decided to switch from Azureus to deluge and so far I'm impressed. It's a nice, slick client with a good gui, just the right amount of options (not bloated like azureus) and the speed is also ok.
BUT...
ONE thing is bothering me : The upload cap doesn't seem to work right: I checked it with "iftop -B" and it the average upload on my machine is always way above the limit I set in Deluge. For example iftop shows me 50 KB upload wenn Deluge is set to 30. 44 when set to 20. and so on. Oddly enough, deluge itself tells me that the upload is well within the limit. But for some reason I tend to trust iftop in this matter more than deluge....
And before you aks:: No, I dont have any other applications with significant upload running. Only Firefox and Gaim. I doublechecked this by quiting deluge and then my overall network upload as shown by iftop drops to zero.

So what gives? Is this a bug or just some strange misconfiguration on my machine? Can others crosscheck this?

My specs: fully updated Ubuntu 7.04 (Feisty Fawn) on a Intel Dual-Core 6600, 2 Gig Ram, downloaded the latest .deb package from the download-page last night (deluge 5.5)

This is important for me cause I'm on a shared internet connection and my buddies wouldn't be so amused when I eat all the bandwith and let nothing left for them...

screenshot showing the obvious difference in upload-rate shown by iftop and deluge-client

upload_diff.jpg (208.36 KiB) Viewed 3508 times

[yodas_brother]

no comments anyone?

[eternalsword]

I'm guessing the difference you are seeing is in overhead. Bytes are sent constantly even when there is no visible upload/download occurring, for such things as initiating handshakes, pex, dht, tracker data, etc. Also, if you have encryption enabled, that will add some additional bandwidth requirements. I wouldn't be too concerned about the shared connection issue. As long as you aren't maxing out the number of connections your gateway can handle, things should be fine.

[yodas_brother]

Thanks for the reply. Yeah, naturally I thought about overhead first too, but figured it couldn't make that much of a difference. But I didn't think about encryption. I guess that would explain it...

[scrooch]

I can confirm this bug. During the firstruntime-setup I entered max upload rate 5kb/s. Then for 3 torrents combined the upload went up to 50kb/s for a longer time. Then I tried the upload/download throttler which comes as plugin. But no results either. I've tried this on several different networks.