Hi,

I've set an upload speed limit in ktorrent 4.2.1 on Kubuntu, but ktorrent indeed saturates my uplink making other applications practically unusable. Summing up all upload speeds shown in the GUI everything looks correct, but network monitor tools show ktorrent flooding the link. I suspect a problem with jobs added via a magnet link. Maybe these jobs' upload banwidths are not considered by ktorrent when it limits the upload speed.

Thanks!

The upload limits only apply to bittorrent protocol data, any other data traffic is not included (so no tracker communication and no DHT). But these protocols which aren't taken into account, should not add that much extra traffic. Tracker announces are sporadic, DHT should be low bandwidth, no actual file data passes over that.

We also do not take into account protocol overhead for underlying protocols like TCP, UDP, IP, ethernet ... This overhead is impossible to know.

It's probably best to leave a 10 to 20% safety margin over values you enter into the ktorrent settings, to account for protocol overhead and the uncapped protocols.

Thanks for the reply.

George wrote:It's probably best to leave a 10 to 20% safety margin over values you enter into the ktorrent settings, to account for protocol overhead and the uncapped protocols.

Thanks for the tip, but I already have a huge margin: my uplink is about 60kBps, the upload limit in ktorrent is set to 15kBps; that's a 300% headroom, and ktorrent still saturates the uplink. Do you think this is normal?

szabolcsszekelyi wrote:Thanks for the reply.

George wrote:It's probably best to leave a 10 to 20% safety margin over values you enter into the ktorrent settings, to account for protocol overhead and the uncapped protocols.

Thanks for the tip, but I already have a huge margin: my uplink is about 60kBps, the upload limit in ktorrent is set to 15kBps; that's a 300% headroom, and ktorrent still saturates the uplink. Do you think this is normal?

Not really, but I can't say much without an analysis of the traffic. Would it be possible to do a wireshark trace when this happens ?