Extremely high traffic overhead

[jdhore]

Whenever i'm running a torrent and it's going at say...300KB/s down, 40KB/s up with a bunch of seeders and leechers, my 2 system monitoring apps say that my computer is using about 350KB/s down, 68KB/s up. When this happens, i'm not doing anything more than having a few IM apps open (no audio or video though), not browsing the web or downloading any files via HTTP/FTP. This happens on every version of Deluge since at least 0.5.5, it happens when i'm even only running 1 torrent, and it also happens at different speeds:

140KB/s speed in Deluge = 165KB/s speed according to monitor apps
300KB/s speed in Deluge = 350KB/s speed according to monitor apps

Also, this issue does not happen when i'm using KTorrent or Azureus and i've been using Deluge and having this problem on Debian Sid and Debian Lenny and Ubuntu Gutsy.

[markybob]

Whenever i'm running a torrent and it's going at say...300KB/s down, 40KB/s up with a bunch of seeders and leechers, my 2 system monitoring apps say that my computer is using about 350KB/s down, 68KB/s up. When this happens, i'm not doing anything more than having a few IM apps open (no audio or video though), not browsing the web or downloading any files via HTTP/FTP. This happens on every version of Deluge since at least 0.5.5, it happens when i'm even only running 1 torrent, and it also happens at different speeds:

140KB/s speed in Deluge = 165KB/s speed according to monitor apps
300KB/s speed in Deluge = 350KB/s speed according to monitor apps

Also, this issue does not happen when i'm using KTorrent or Azureus and i've been using Deluge and having this problem on Debian Sid and Debian Lenny and Ubuntu Gutsy.

this is simply because those clients include the overhead in their rates and we do not. if they didnt show the overhead, and just gave you the bare rates as we do, it'd be the same thing. encryption alone is a huge overhead. there's plenty more in the rest of the protocol, too.

[Ux64]

Yep. I agee with markybob about this one.

It's not deluge related problem, it's bittorrent related kind of problem. Protocol overhead is a lot bigger than I previously thought. If you want to see what I wrote about this same "problem" earlier please check this thread.

http://forum.deluge-torrent.org/viewtop ... =bandwidth

I was used to eMule which got smaller overhead / connection. And it usually didn't even use all connections, so limit could be ridiculously high. But bittorrent clients remains connected to swarm, even if they don't transfer any data. And also high number of smaller blocks cause a lot more "reporting" traffic between peers, especially when you're still downloading quite fast.

It's not a problem when you know it. Just set low enough connection limit and reserve enough bandwidth for overhead.

[Sharky]

And why don include this overhead in upload/download? It's part of the bandwidth

[Ux64]

And why don include this overhead in upload/download? It's part of the bandwidth

eMule includes all traffic to BW usage, including DHT (kad) traffic.

I haven't studied uTorrent troughly.

But as you find out from my report, overhead it's very high. If you got many connections. It's good idea to limit connections to reasonable number. Usually a small number can anyway max out bandwidth easily. Like 20 connections etc. using more than 100 connections is just way too much, as I described in my other thread.