- [17:45] <Y> There's bugs in uTorrent recently that cause that I believe
- [17:45] <Y> I can't my finger on WHAT exactly triggers bad results, I just have lots of (indirect) evidence that there is.
- [17:46] <Z> yeah, ever since 1.8.2+
- [17:46] <Z> 1.8.2 worked great
- [17:46] <Y> mention that in open chat :)
- [17:46] <Y> I've heard a few offhanded remarks from alus and other devs that various changes were made post v1.8.2
- [17:46] <Y> for instance, how uTP was handled.
- [17:47] <Z> yeah
- [17:47] <Y> bt.trans_disposition before that was only 0 or 255 typically
- [17:47] <Z> yeah i remember that
- [17:47] <Y> I'm hunting a very strange bug...one where torrents aren't starting/downloading when they should.
- [17:48] <Y> Xapti in fact seems to exhibit some/most of that bug.
- [17:48] <Z> what were the major changes from 1.8.2+
- [17:48] <Y> I haven't seen it on torrents I've done, but I generally only seed.
- [17:48] <Z> cant they go back?
- [17:48] <Y> uTP changes galore, total rewrite of the networking engine starting in v1.8.5 (actually v1.9 came first)
- [17:49] <Y> udp trackers in v2.0
- [17:49] <Y> uTP NAT hole-punching in v2.0
- [17:49] <Y> Webui changes
- [17:49] <Y> BT DNA was added as well, but not enabled in any fashion supposedly...in v1.8.5 or v2.0
- [17:50] <Y> There's been some really horrid half open handling issues by uTorrent between v1.8 and 2.0
- [17:50] <Y> one of the most recent that was decently documented was the HTTPS trackers that timeout were being counted as half open connections even hours later.
- [17:51] <Y> So 1 failed HTTPS tracker could soon mean uTorrent quits making outgoing connections. People's insane workaround was to keep increasing how many half open connections uTorrent tries to make at once.
- [17:51] <Z> yeah, I had to set mine to like 1000
- [17:51] <Z> :(
- [17:52] <Z> looks like im gonna go back to 1.8.5
- [17:52] <Y> I lower mine typically to 4.
- [17:52] <Z> for the time being
- [17:52] <Z> boo
- [17:52] <Y> why?
- [17:52] <Y> I only run 10-30 torrents at a time
- [17:52] <Z> because of my upload speed
- [17:52] <Z> i was running 2 torrents
- [17:52] <Y> upload speed cares not
- [17:52] <Z> and not getting no where near the same speeds i was getting when i was using 1.8.5
- [17:52] <Y> half open connections do *NOT* count uTP, Teredo, incoming connections
- [17:53] <Y> half open only applies to outgoing TCP peers/seeds and HTTP/HTTPS tracker updates
- [17:53] <Y> if you're unfirewalled, your incoming connections should be far more common.
- [17:53] <Z> no, not firewall
- [17:54] <Y> The big problem is uTorrent will continually retry dead and busy ips with a high half open, helping nobody really. It only very slowly backs off if the line is dead.
- [17:55] <Z> has this always been the case?
- [17:55] <Z> even with previous versions?
- [17:55] <Y> Routers can "stuff up" their iptables due to these failed connection attempts, and then bomb softly or craptacularly.
- [17:55] <Y> some ways yes, some ways no.
- [17:55] <Y> The big problem NOW is bt.connect_speed
- [17:55] <Y> that's how FAST to make outgoing connections in connections per second.
- [17:56] <Z> should i make some changes to mine?
- [17:56] <Y> Thanks to Teredo and uTP not being limited by net.max_halfopen...the number of in-progress outgoing connection attempts at once could soar from the previous default limit of 8 to 300!
- [17:57] <Y> That's because bt.connect_speed was 20 new connections per second
- [17:57] <Y> but the failed ones won't "give up" and time out typically for ~15 seconds.
- [17:57] <Y> 20 x 15 = 300
- [17:58] <Y> In practice I was seeing >200 in progress at once often when running "busy" torrents with lots of seeds/peers.
- [17:58] <Y> uTorrent now has stricter (TOO STRICT) handling of upload slots, especially for a line such as yours.
- [17:59] <Y> Each active torrent that has even 1 peer is treated as though it has max upload slots for limiting purposes.
- [17:59] <Z> yeah :( i set my slots to 40
- [17:59] <Z> should i increase my slots?
- [17:59] <Y> no, try decreasing default upload slots to 20 but raise upload slots on an extremely busy torrent as needed.
- [18:00] <Y> Otherwise the torrents with just 1 peer counts as having 40 upload slots...then current total upload speed is used to determine max allowed upload slots per torrent.
- [18:00] <Z> ahhhh
- [18:00] <Z> ok
- [18:01] <Y> Even at 5000 KB/sec, uTorrent probably is kicking max upload slots down to <20 :(
- [18:01] <Y> except it's a vicious cycle...speed briefly drops lower = fewer upload slots per torrent allowed!
- [18:04] <Y> this dovetails into another flaw/bug, when upload slots = 1 per torrent
- [18:05] <Y> The optimistic unchoke "roaming" upload slot is always used first, which jumps between peers and doesn't upload as long to one as 'regular' upload slots.
- [18:05] <Y> uTorrent was programmed to change which peer that uploads to at 1 or 2 minute intervals, so EVERY torrent changes all that the same time.
- [18:06] <Y> ...which triggers another upload speed drop-off even if upload slots are still above 1 per torrent.
- [18:06] <Y> And I've even seen torrents with just 1 peer not being uploaded to at all because uTorrent tried to switch to upload to a different peer. :P
- [18:11] <Y> read this to find out more about half open and upload slots: http://forum.utorrent.com/viewtopic.php?pid=417225#p417225
- [18:11] <Z> thanks