DHT and PEX not limited by Turtle mode

[Aethylred]

When using Turtle mode to schedule idle times for transmission, transmission will continue to do DHT and PEX queries and responses.

This can add up to significant amounts of traffic (Gigabytes!) daily.

This behavior can be observed by setting Turtle bandwidth to 0 upload and download, and switching DHT and PEX on and off while monitoring network traffic.

I suggest that:

• these features need to conform to the bandwidth limits
• these features can be disabled during turtle mode

Though this bug does not impair Transmission's functionality it can cause unintentional effects on a Transmissions network performance, or their Internet bill if they have per Gigabyte charges.

[jordan]

Hi Aethylred,

Thanks for the suggestion.

The behavior you're describing is intentional -- we only include piece data in our speed computations. When we included protocol overhead, several people complained that the torrent didn't seem to be downloading as quickly as the speed display indicated. :)

I strongly doubt that PEX will add up to Gigabytes daily. DHT probably has more overhead than PEX, but DHT can be disabled if you are short on bandwidth.

[Aethylred]

Thanks for your response, but increasingly "disable DHT" means "disable bittorrent" :(

I understand not adding PEX and DHT to speed calculations, but what'd sort this out would be having some options:

alt-bandwidth-pex-disable

alt-bandwidth-dht-disable

That just shuts them off in alt-bandwidth (aka turtle) mode.