First of all, let me thank you so very very much for this incredible application. I really enjoy the design and easy of use of everything on Transmission.
Now, for the request.
One of the things we all know is that the more connections you have the faster you'll download or upload things. However, the protocol overhead is high and that can lead to use more bandwidth to protocol controls than actually to data transfers.
Here is my example: I have 2Mb download and 384Kb upload. Whenever I let transmission work with a high amount of connections, my upload bandwidth is consumed completely, around 45KB/s but transmission itself only shows like 15 or 20KB of upload, all the rest is protocol control.
A way to solve this is to lower your connections, and thus the overhead lowers with it.
Speed Limit allows us to restrict how much do we want to be used for upload or download but as far as I know it doesn't count the protocol overhead. We could have an option on it also for Connections.
It would be great if we had some more options to control our connections. For example:
- In Bandwidth, we could have an option to limit connections per torrent when in Speed Limit. There is already an option for connections per torrent individually and for new ones, however, this could help close the gap and have better control of the overhead in Speed Limit. Here is an idea:
- In Transfers --> Management, despite "Seeding with a maximum of: XXX active transfers" we could also have a "Seeding with a maximum of: XXX connections per torrent", which would allow a client to upload torrents with less overhead due to fewer connections and to those receiving it the speed would be higher.
Right now, I perform those two operations manually every time a torrent finishes to download and starts to seed and every time I go into Speed Limit so I don't have so much overhead.
I hope this is somehow useful and if this was suggested before, sorry, I couldn't find it.
Thank you. =)