Registered Member
|
I've set Ktorrent's global limit to 22 kB/s, but MRTG (SNMP) data gathered on my outbound network interface shows around 29 kB/s load. I'm sure there are no other apps running, because stopping Ktorrent drops the load to a mere 200-300 Bps. Isn't the 25-27% surplus a bit off for a typical TCP/IP overhead? I'd assume 23-24 kB/s, but not 29. What is Ktorrent doing with the rest of the bandwidth?
Version: 3.3.4 |
Moderator
|
Connecting to trackers, DHT, connecting to peers, DNS resolving of peers, and then you still have all the TCP and IP overhead.
|
Registered Member
|
Thank you for responding. The "Resolve hostnames of peers" checkbox is unchecked, so it's not the DNS load. I'd guess we might consider the "connecting to trackers/peers" load as negligible. So it's DHT taking up the largest part of the loaf, even though the "Use DHT to get additional peers" is unchecked per default. I'm stumped. |
Moderator
|
It's probably the overhead of TCP and IP.
|
Registered Member
|
Network-level (Ethernet+PPPoE+TCP/IP) overhead is normally less than 5% of the data flow, not 30%
|
Moderator
|
And your assumption is based on which measurements ? If you are not downloading or uploading to a peer, there will be regular bittorrent protocol messages (like a peer telling you it has a chunk), these messages are small, and thus will have a much higher overhead then transferring pieces. Also if you are uploading at a rate of a couple of KB/s to a peer, it will have more overhead percentage wise then uploading at for example 100 KB/s. It all depends if you can make your packets as big as the MTU, if this is not the case due to lack of data, your overhead percentage increases. |
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]