Slower seed speeds with utorrent 2.0

[houkouonchi]

Previously posted in troubleshooting before I noticed a section specifically for speed issues.

I was using 1.8.2 until the whitelist was removed on the tracker I primarily seed at and was forced to upgrade to 2.0. Since using 2.0 I noticed I am getting much lower speeds (lower than I have seen in quite some time). Before I would average anywhere from 100-200 megabits and averaged around 130 megabits or so (during times I had utorrent uncapped). Just today I upgraded to 2.0 and you can see the difference from the weekly bandwidth graph:

The spike on Wednesday was from something else and on Thursday I noticed my speeds drop and drop from the fact utorrent wasn't contacting the tracker anymore. When it bumped up again is when I changed to version 2.0 but it didn't increase that much and after a while it started decreasing again. You can see this better on the daily graph:

Utorrent 1.8.2 was likely blocked at around 17:00 on the graph... speeds decreased until around 21:00 when I upgraded to utorrent 2.0. Things seemed bottlenecked for a while until I disabled the bt.tcp_rate_control at around 23:00. Things got slightly better but ended up dropping down again.

The type of speeds I am getting now seem kind of pathetic to what I am used to and the main difference i see is the upgrade to 2.0. Can anyone thing of any changes from 1.8.2 -> 2.0 that would cause a great speed difference on very high speed connections or things i can try to optimize seed speeds?

Update:

Ok so still getting slow speeds. Its even more obvious as my previous network graph included an interface that wasn't BT traffic and here is the graphs from pretty much just BT:

You can really see how the speed dropped. Here is the daily:

The tracker I was on which suddenly removed 1.8.2 from their whitelist (not sure why) they still had 1.7.7 on their whitelist so I went ahead and downgraded to that and my speeds went up a lot. You can really see the huge difference from 2.0 -> 1.7.7. The two above graphs above were literally right after switching to 1.7.7 and here is after running 1.7.7 for a while:

Update 2:

And here is another view of the switch after running 1.7.7 for a while, definitely a huge difference:

[Switeck]

1st link in my signature.

...I'm not getting a feel from your graphs about what your uTorrent settings are (maybe a bug's trigger?) or how many torrents you have running or the torrent swarm's composition.

Are there any/many IPv6 ips mixed in?

Obviously uTP and Teredo/IPv6 won't work in v1.7.7 -- but maybe native IPv6 does in v1.7.7?

[houkouonchi]

Seeding about 1.5 TB of files in around 160 torrents. I basically have the settings maxed so the number of connections shouldn't be limited by utorrent, IE:

1,000 max active torrents

12,000 max global connections

2,000 max connected peers (per torrent)

1,000 Upload slots per torrent

The most important network graph is this one:

This one shows the change from 2.0 to 1.7.7 at 2:30 AM on the graph. I am getting almost as good as speeds with 1.7.7 as I did with 1.8.2 and I am pretty sure I had UTP and all the same settings as I did with 2.0 so I am not sure what would have changed on that end.

ipv6 traffic is pretty minimal as it only equates to around 5-15 megabits of bandwidth tops. This is with native ipv6.

You say UTP wont' work in 1.7.7 but for quite a while I used 1.8.2 for a long time which gave me good speeds and the only reason I went to 1.7.7 is because 1.8.2 was blacklisted and 2.0 gave me bad speeds.