zoosraka.blogg.se

Optimizing deluge client settings
Optimizing deluge client settings






As many settings as possible were disabled in the various BT clients - no DHT, LPD, trackers, uTP, and even half open connections were set as low as possible since only 1 connection had to be made. Multiple seeds to multiple peers could be faster depending on program designs, but would certainly cause a much larger CPU load. The test is a single TCP connection at a time - 1 seed to 1 peer, which may show severe pipelining issues.

#Optimizing deluge client settings utorrent#

Unless stated otherwise, these speeds are all UPLOAD speeds to uTorrent v2.2.1. CPU is Intel i5 650 3.2 GHz - dual core with hyperthreading. The files being transferred are all on a ramdrive (almost 5 GB DDR3), so effectively ruling out slow drives as well. Using multiple BitTorrent clients on the same computer over 127.0.0.1 loopback. Torrent speeds are variable and erratic by definition, depending on a multitude of factors (number and speed of seeds, number and speed of downloaders, relative location of seeds and downloaders, network congestion, time of the day and time zones, local software issues, and many others). Please do note that testing torrent client speeds is always relative, since you can't necessarily expect the same exact performance out of two consecutive tests, even if everything else in the test is the same. It's easy to test whether your security software is the cause by simply temporarily disabling it to see if it changes anything (but I don't see why it would be, since you already said your ports are forwarded, and that would be the one factor which would cause a problem with speeds). I would try Tixati's optimization guide, if you haven't yet: Settings such as the maximum number of connections and peers per torrent, or the port(s) you're using are some of the things which CAN affect it.

optimizing deluge client settings

Torrent clients do not limit connection speeds, unless you configure them to. There's no reason why ANY torrent client shouldn't be able to use up your full connection speed, whatever it is (even a relatively slow one, such as yours).






Optimizing deluge client settings