- Deluge client half open connections update#
- Deluge client half open connections utorrent#
- Deluge client half open connections software#
Tracker update time can be changed too from libtorrent, but no matter if setting that lower than the default 10 or 30 min's(can't remember), then the tracker itself enforces a minimum re-announce time.
Deluge client half open connections software#
It's not for anything practical as my downloads usually takes under 5 - 10 mins, but just like having every software as optimized for the job as possible. I am just interested in maxing my speed out fastest, so faster downloading-time in total. Personally, i can't accept incoming connections because using a socks5 proxy, though can of course still upload through outgoing connections. Having it adjustable means also to be able to set it lower ) Anyway, for me, the bottom-line is that as deluge and uttorrent supports it, then I would like qbt to support it too. Thanks for your insights again Seeker2, I appreciate it.
Deluge client half open connections utorrent#
uTorrent has bt.connect_speed set to 1 and net.max_halfopen set to 8.and it's running 50+ other torrents as well. (maybe 2-20 seeds and 25-50 peers) I can swap computers and/or internet connections and qBT still takes longer and connects to fewer peers. There's probably not enough peers+seeds for the other peers to max out their connections.
On a busy large torrent I am seeding on multiple computers and 2 internet connections, uTorrent connects to 20+ peers.qBT struggles to connect to 5. Makes peer-seed connection testing difficult and slow.and that's when I know the connections WORK! I can stop and restart a torrent and it won't even retry ips or do tracker updates for minutes at a time. QBT doesn't operate anywhere near that hard-coded speed limit. QBT's default limit of 20 for connect speed could reach 70+k in 1 hour.were there no other limitations.
UTP (being UDP based) isn't technically limited by half open issues (that TCP connections have) unless a BT client is programmed to limit uTP connection rates to match regular (TCP-using non-uTP) peer/seed connections. High numbers on each are extremely overrated so long as you can accept incoming connections.īt.connect_speed could be set to 1 and still be limited sometimes with net.max_halfopen set to 8, especially on public torrents with many firewalled and disconnected peers. I've done extensive testing of bt.connect_speed and net.max_halfopen settings in uTorrent. It's not an advantage for Deluge to overload someone's connection. I'm in favor of adding the option in qBitTorrent, but strongly recommend against the levels the high-performance-seed preset uses. Reply to that said: "When Deluge is downloading it takes away all my bandwidth so i'm unable to browse properly." "In my tests, the options of high-performance-seed didn't help the downloading-time for me, and all those extra libtorrent connections takes bandwith away from you too" (poster's name looks familiar somehow.) :(ĭeluge's plugin for high-performance-seed preset is nuts - really Denial-of-Service attack level. The benefits for this on for big and very busy torrents are generally negative. Yeah, I can see why connection_speed set to 20 isn't enough.Īfter less than 5 minutes, any value above about 5 just means retrying peers/seeds that are dead, firewalled, or already at connection max.
You have 150 megabits/second upload?! (I only have ~10 mbit/sec UL) People reading this may not know the implications of changing this value.
0 kommentar(er)
