Question concerning transfer rates

[motion]

Hello everyone!

I've modified libtorrent-rasterbar5 to interpret the upload transfer limit "-1" as "0". While this seems to work, Deluge still shows me uploaded data (~1KB for each downloaded 10MB). So I'm wondering if this data is just the protocol/IP overhead and Deluge adds this to the transferred data value or if I'm still uploading "real" content.

TIA for your help!

@ the moralizers: I'm not a (typical) leecher, I just like to stay in full control (mobile data transfer is still very expensive).

[johnnyg]

I'm assuming you're using the GTK UI.

In the status bar you should see an up/down arrow which shows protocol traffic.
All speeds reported by deluge in the main window are data speeds.

The reason you're still uploading stuff is because 0 and -1 both mean unlimited to libtorrent.

[motion]

I'm assuming you're using the GTK UI.

Yes, I do. Sorry for not mentioning.

In the status bar you should see an up/down arrow which shows protocol traffic. All speeds reported by deluge in the main window are data speeds.

Thanks, speeds seem ok: while there is some protocol traffic (2-7 KiB/s up), the upload speed stays at 0.0 KiB/s (there are some short ~1 KiB/s periods every now and then - not yet investigated where they're coming from). Yet, the "Uploaded: <total> (<session>)" value in the "Status" tab constantly raises (by small amounts). Does this value include protocol data?

The reason you're still uploading stuff is because 0 and -1 both mean unlimited to libtorrent.

That's what I've changed in libtorrent-rasterbar5 (they do something like 'if (limit_to_set <= 0) limit = maxint'). If the protocol data's not included in the "Uploaded" value, then I've screwed something up.

Edit:

After more observing, I'd say: no, the protocol traffic is not added to the "Uploaded:" value. Seems I need to take a closer look at libtorrent or live with this really minimal upload.