Hi,

I noticed a bug in 2.2rc1 version, now it don't seems to respect at all the upload speed limit i set.

See the screenshot here :
http://rapsys.free.fr/ktorrent/2007.1/2 ... orrent.png

My Maximum upload bandwith is 800KB/s.
I set (as you can see on screenshot) upload bandwith to 50KB/s.

But the upload bandwith used is close to maximum (650-800KB/s).
(see the knetmon red square at bottom, the full height is 800KB/s scale).

There seems to have something wrong with ktorrent calculation, as it say he upload at 51KB/s O_o
I suspect that ktorrent only count the bandwith used for data upload, not tcp connection bandwith used.

I noticed an other UI bug that time :
http://rapsys.free.fr/ktorrent/2007.1/2 ... orrent.png

The ui of torrent specific speed limit has an insuficient height here.

Plz fix it if possible.

First of all knetload measures in kilobits per second, KT does in kilobytes per second. So lets divide by 8 and then we can compare.

KTorrent only measures the data it sends out, it does not take into account IP and TCP headers. Taking this overhead into account is very difficult. KT has no idea how many TCP retransmissions happen for example.

Connection setups, DHT and tracker announces are also not included in the calculated upload speed.

At what layer is knetload measuring ? IP layer ? Ethernet layer ? PPP layer ?

Btw, concerning that ui bug, I think you linked to the wrong screenshot, but I think it is the same problem we had with the scan dialog.

The name of the torrent gets filled in but the size doesn't get updated, if the name spans multiple lines, there is a problem.