Hey guys!
I have a question:
First little explanation:
I have a torrent: it is downloading at 60KiB/s and uploading at 80KiB/s. I don't want to seed this torrent to much, so I limit the upload speed to 5 KiB/s. And immediately my download speed is going down to 2-3 ( less then 10 KiB/s ). I was a little confused so I changed the upload speed to unlimited and then both upload and download rates got back to normal ( download 60 and upload 80 ).
My question:
Why does deluge has somekind of upload/download speed correlation mechanism built in? Is this on purpose? is this a bug?
Krystian Kichewko
ps. This is related to both max upload speed on 1 torrent and to max upload speed on whole deluge daemon.
Upload download speed correlation
Re: Upload download speed correlation
Hi,
By limiting the upload speed you effectively limit the download also, because TCP is a two way protocol (you need confirmations from your peers about sent packets). There is an announcement by andar explaining this:
http://forum.deluge-torrent.org/viewtop ... =7&t=11165
As to why you can't set the limit only for outgoing traffic and NOT the incoming protocol overhead beats me. I think it is decided by libtorrent developers.
By limiting the upload speed you effectively limit the download also, because TCP is a two way protocol (you need confirmations from your peers about sent packets). There is an announcement by andar explaining this:
http://forum.deluge-torrent.org/viewtop ... =7&t=11165
As to why you can't set the limit only for outgoing traffic and NOT the incoming protocol overhead beats me. I think it is decided by libtorrent developers.
Re: Upload download speed correlation
There is an option to not rate limit ip overhead in the Bandwidth settings.solarsd wrote:Hi,
By limiting the upload speed you effectively limit the download also, because TCP is a two way protocol (you need confirmations from your peers about sent packets). There is an announcement by andar explaining this:
http://forum.deluge-torrent.org/viewtop ... =7&t=11165
As to why you can't set the limit only for outgoing traffic and NOT the incoming protocol overhead beats me. I think it is decided by libtorrent developers.