I just updated to v2.3 a couple of days ago and my download speeds plummeted! I generally get 100K to 200K per download (maxing out around 500k-600K for all downloads). Suddenly I was getting 20-40K total for 3 torrents. I thought it was my ISP at first and tried it at another location. Speeds were still terrible. I updated to v2.31, increased allowed peers to 200, still terrible. I uninstalled and reverted to 2.22 and everything worked great! I'm currently downloading two torrents at a combined rate of 350K-400K.
So what gives with 2.3?
I'm running on OS X 10.6.7 on a MacBook Pro i5 2.53GHz (2010).
And yes, the port is closed. But it's closed on both versions!
Would love to use the latest version but won't update until I know it won't destroy performance. Is this a bug? Should I report it officially?
2.3 is Much Slower than 2.22
Re: 2.3 is Much Slower than 2.22
I'm not seeing this behavior. What should I do to reproduce it? Was it just random chance?S_Jacob wrote:I updated to v2.31, increased allowed peers to 200, still terrible. I uninstalled and reverted to 2.22 and everything worked great! I'm currently downloading two torrents at a combined rate of 350K-400K.
The biggest change to 2.3x that might affect speed is the addition of uTP support. You might want to try disabling that in the preferences and see if that makes any difference.
Re: 2.3 is Much Slower than 2.22
i haven't noticed any speed decrease with 2.31, and i have uTP enabled.
Re: 2.3 is Much Slower than 2.22
Same here, uTP is pretty fast. The reason I suggested a test run w/o uTP is that's the biggest change between 2.22 and 2.30.quinx wrote:i haven't noticed any speed decrease with 2.31, and i have uTP enabled.
Re: 2.3 is Much Slower than 2.22
I have the same issue of slowness if uTP is turned on.
The first new download after upgrading from 2.22 to 2.31 ran at 1% of normal speeds. Very few peers were connecting. After reading this thread I went and turned off uTP and speed went back to normal. As a test, I turned uTP back on and got this error message in the log:
2011-05-18 13:37:21 -0700 tr-udp.c:56 [Error] UDP: Failed to set receive buffer: No buffer space available
2011-05-18 13:37:21 -0700 tr-udp.c:75 [Error] UDP: Failed to set receive buffer: requested 4194304, got 32768
I'm running OS 10.6.7 on an Intel iMac with 2G RAM.
The first new download after upgrading from 2.22 to 2.31 ran at 1% of normal speeds. Very few peers were connecting. After reading this thread I went and turned off uTP and speed went back to normal. As a test, I turned uTP back on and got this error message in the log:
2011-05-18 13:37:21 -0700 tr-udp.c:56 [Error] UDP: Failed to set receive buffer: No buffer space available
2011-05-18 13:37:21 -0700 tr-udp.c:75 [Error] UDP: Failed to set receive buffer: requested 4194304, got 32768
I'm running OS 10.6.7 on an Intel iMac with 2G RAM.
Re: 2.3 is Much Slower than 2.22
Yes I had the same problem, both 2.3 and 2.31 2.2 is fine
2011-05-18 22:02:25 +0100 tr-udp.c:56 [Error] UDP: Failed to set receive buffer: No buffer space available
2011-05-18 22:02:25 +0100 tr-udp.c:75 [Error] UDP: Failed to set receive buffer: requested 4194304, got 42080
2011-05-18 22:02:44 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 21 to 188.236.152.184, port 42770 (errno 61 - Connection refused)
2011-05-18 22:02:44 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 21 to 188.236.152.184, port 42770 (errno 61 - Connection refused)
ETC...
ETC...
2011-05-18 22:05:50 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 24 to 31.176.128.13, port 22839 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 20 to 212.118.143.38, port 33680 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 20 to 212.118.143.38, port 33680 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:05:52 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:06:56 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
ETC..
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 46.250.168.18, port 20676 (errno 61 - Connection refused)
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 46.250.168.18, port 20676 (errno 61 - Connection refused)
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 2.25.184.63, port 26498 (errno 61 - Connection refused)
ETC..
ETC..
2011-05-18 22:17:24 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 14.207.66.201, port 52653 (errno 61 - Connection refused)
2011-05-18 22:17:51 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:17:51 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
ETC..
2011-05-18 22:23:14 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 29 to 219.85.187.200, port 42387 (errno 61 - Connection refused)
2011-05-18 22:23:14 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 29 to 219.85.187.200, port 42387 (errno 61 - Connection refused)
2011-05-18 22:02:25 +0100 tr-udp.c:56 [Error] UDP: Failed to set receive buffer: No buffer space available
2011-05-18 22:02:25 +0100 tr-udp.c:75 [Error] UDP: Failed to set receive buffer: requested 4194304, got 42080
2011-05-18 22:02:44 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 21 to 188.236.152.184, port 42770 (errno 61 - Connection refused)
2011-05-18 22:02:44 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 21 to 188.236.152.184, port 42770 (errno 61 - Connection refused)
ETC...
ETC...
2011-05-18 22:05:50 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 24 to 31.176.128.13, port 22839 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 20 to 212.118.143.38, port 33680 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 20 to 212.118.143.38, port 33680 (errno 61 - Connection refused)
2011-05-18 22:05:52 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:05:52 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:06:56 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
ETC..
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 46.250.168.18, port 20676 (errno 61 - Connection refused)
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 46.250.168.18, port 20676 (errno 61 - Connection refused)
2011-05-18 22:16:57 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 2.25.184.63, port 26498 (errno 61 - Connection refused)
ETC..
ETC..
2011-05-18 22:17:24 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 19 to 14.207.66.201, port 52653 (errno 61 - Connection refused)
2011-05-18 22:17:51 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
2011-05-18 22:17:51 +0100 torrent.c:534 [Error] *********************************************************************: "Connection failed"
ETC..
2011-05-18 22:23:14 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 29 to 219.85.187.200, port 42387 (errno 61 - Connection refused)
2011-05-18 22:23:14 +0100 net.c:286 [Error] Transmission: Couldn't connect socket 29 to 219.85.187.200, port 42387 (errno 61 - Connection refused)
Re: 2.3 is Much Slower than 2.22
That big list of "Connection refused" is probably being caused by peers who are firewalled and aren't accepting incoming connections... if so, that's just Life With BitTorrent and has nothing to do with uTP or what version you're running.
Re: 2.3 is Much Slower than 2.22
Then explain why that big list of connections works just fine with 2.2? I've been using Transmission for two years now and nothing changed except the upgrade to 2.3 then 2.31 and neither worked. There were multiple peers to conenct to and a miserly download of 0.3 - 1.2 then connection refused but the network was swamped with connections that weren't connecting and no internet connection was possible from browser or mail application only Pausing the error on the connection had any effect, limiting the upload or download had no effect.
If this helps:
Software version 10.6.7 build 10J869
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 10 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
There were no crash reports because the transmission didn't crash it just kept running and doing nothing.
2011-05-19 17:47:11 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 74 to 94.200.43.132, port 24434 (errno 61 - Connection refused)
2011-05-19 17:47:12 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 25 to 79.106.109.168, port 34595 (errno 61 - Connection refused)
2011-05-19 17:47:15 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 77 to 46.129.67.162, port 32928 (errno 61 - Connection refused)
2011-05-19 17:47:17 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 114 to 101.109.88.3, port 6881 (errno 61 - Connection refused)
2.2 is working in so much as can download and upload even though presently only seeding still getting connection errors due to refusals but they are varying whereas before they were multiple on the same socket. I expect to get peersblocked either from firewalls or Peer guardian. But with 2.31 the program brought the network down and 2.2 doesn't.
Otherwise I luv the software and I should really donate
If this helps:
Software version 10.6.7 build 10J869
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 10 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
There were no crash reports because the transmission didn't crash it just kept running and doing nothing.
2011-05-19 17:47:11 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 74 to 94.200.43.132, port 24434 (errno 61 - Connection refused)
2011-05-19 17:47:12 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 25 to 79.106.109.168, port 34595 (errno 61 - Connection refused)
2011-05-19 17:47:15 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 77 to 46.129.67.162, port 32928 (errno 61 - Connection refused)
2011-05-19 17:47:17 +0100 net.c:341 [Error] Transmission: Couldn't connect socket 114 to 101.109.88.3, port 6881 (errno 61 - Connection refused)
2.2 is working in so much as can download and upload even though presently only seeding still getting connection errors due to refusals but they are varying whereas before they were multiple on the same socket. I expect to get peersblocked either from firewalls or Peer guardian. But with 2.31 the program brought the network down and 2.2 doesn't.
Otherwise I luv the software and I should really donate
Last edited by chompy on Thu May 19, 2011 5:03 pm, edited 2 times in total.
Re: 2.3 is Much Slower than 2.22
I can't say its exactly the same, but it seems likely similar given that within the hour I had installed uninstalled Transmission 2.31 twice, and 2.3 once and both gave the same problem. Nothing else had changed and I switched off PG Little Snitch etc to rule that out. Deleted the original torrents re downloaded them and same problem. Phoned a friend he upgraded his to 2.31 and it worked fine...
Re Installed 2.22 and connected to the same torrents and everything worked fine with PG an LS running as well.
Re Installed 2.22 and connected to the same torrents and everything worked fine with PG an LS running as well.
Re: 2.3 is Much Slower than 2.22
Upgraded to 2.31 this morning and made changes to the µTP it is now downloading without hanging the network.
Thank you guys.
And I see from this post the root issue may be the buffer?
Thank you guys.
And I see from this post the root issue may be the buffer?
x190 wrote:1. Does this failure effect its performance?
2. If so, how can it be fixed?It's a known issue and devs have chosen not to change the code at this point. If you have Xcode installed or know how to build from source you can change the source code as you wish.what it means and how to fix it
https://trac.transmissionbt.com/ticket/4207#comment:9
https://trac.transmissionbt.com/ticket/2338#comment:74
...or you can try disabling µTP in Prefs->Network.(The failure shouldn't harm much, though, it'll just reduce performance of µTP on busy systems.)
Re: 2.3 is Much Slower than 2.22
Sure.
Router Airport Extreme
======
Network
peer communication
disabled µTP as suggested
======
Peers
Glabal maximum 100
Max connections new transfers 40
use (PEX)
use (DHT)
Encryption prefer
Blocklist not enabled as using PG
=========
recent log at startup if useful.
2011-05-21 11:34:14 +0100 session.c:706 [Info] Transmission: Transmission 2.31 (12441) started
2011-05-21 11:34:14 +0100 cache.c:258 [Debug] Cache: Maximum cache size set to 4.00 MB (256 blocks)
2011-05-21 11:34:14 +0100 rpc-server.c:805 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2011-05-21 11:34:14 +0100 net.c:373 [Debug] Transmission: Bound socket 12 to port ***** on 0.0.0.0
2011-05-21 11:34:14 +0100 net.c:373 [Debug] Transmission: Bound socket 13 to port ***** on ::
2011-05-21 11:34:14 +0100 fdlimit.c:808 [Debug] Transmission: setrlimit( RLIMIT_NOFILE, 1024 ); FD_SETSIZE = 1024
2011-05-21 11:34:14 +0100 fdlimit.c:816 [Debug] Transmission: socket limit is 100
2011-05-21 11:34:14 +0100 tr-dht.c:276 [Debug] DHT: Initializing DHT
2011-05-21 11:34:14 +0100 tr-dht.c:305 [Info] DHT: Reusing old id
2011-05-21 11:34:14 +0100 tr-dht.c:153 [Info] DHT: Bootstrapping from 105 nodes
2011-05-21 11:34:14 +0100 tr-dht.c:330 [Debug] DHT: DHT initialized
2011-05-21 11:34:14 +0100 rpc-server.c:805 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2011-05-21 11:34:14 +0100 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2011-05-21 11:34:14 +0100 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2011-05-21 11:34:14 +0100 upnp.c:105 [Debug] Port Forwarding (UPnP): upnpDiscover failed (errno 65 - No route to host)
2011-05-21 11:34:14 +0100 upnp.c:125 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Unknown error: 0)
2011-05-21 11:34:14 +0100 upnp.c:128 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2011-05-21 11:34:14 +0100 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
..
..
2011-05-21 11:34:15 +0100 fdlimit.c:663 [Debug] Transmission: SO_SNDBUF size is 65536
2011-05-21 11:34:15 +0100 fdlimit.c:665 [Debug] Transmission: SO_RCVBUF size is 65536
Router Airport Extreme
======
Network
peer communication
disabled µTP as suggested
======
Peers
Glabal maximum 100
Max connections new transfers 40
use (PEX)
use (DHT)
Encryption prefer
Blocklist not enabled as using PG
=========
recent log at startup if useful.
2011-05-21 11:34:14 +0100 session.c:706 [Info] Transmission: Transmission 2.31 (12441) started
2011-05-21 11:34:14 +0100 cache.c:258 [Debug] Cache: Maximum cache size set to 4.00 MB (256 blocks)
2011-05-21 11:34:14 +0100 rpc-server.c:805 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2011-05-21 11:34:14 +0100 net.c:373 [Debug] Transmission: Bound socket 12 to port ***** on 0.0.0.0
2011-05-21 11:34:14 +0100 net.c:373 [Debug] Transmission: Bound socket 13 to port ***** on ::
2011-05-21 11:34:14 +0100 fdlimit.c:808 [Debug] Transmission: setrlimit( RLIMIT_NOFILE, 1024 ); FD_SETSIZE = 1024
2011-05-21 11:34:14 +0100 fdlimit.c:816 [Debug] Transmission: socket limit is 100
2011-05-21 11:34:14 +0100 tr-dht.c:276 [Debug] DHT: Initializing DHT
2011-05-21 11:34:14 +0100 tr-dht.c:305 [Info] DHT: Reusing old id
2011-05-21 11:34:14 +0100 tr-dht.c:153 [Info] DHT: Bootstrapping from 105 nodes
2011-05-21 11:34:14 +0100 tr-dht.c:330 [Debug] DHT: DHT initialized
2011-05-21 11:34:14 +0100 rpc-server.c:805 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2011-05-21 11:34:14 +0100 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2011-05-21 11:34:14 +0100 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2011-05-21 11:34:14 +0100 upnp.c:105 [Debug] Port Forwarding (UPnP): upnpDiscover failed (errno 65 - No route to host)
2011-05-21 11:34:14 +0100 upnp.c:125 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Unknown error: 0)
2011-05-21 11:34:14 +0100 upnp.c:128 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2011-05-21 11:34:14 +0100 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
..
..
2011-05-21 11:34:15 +0100 fdlimit.c:663 [Debug] Transmission: SO_SNDBUF size is 65536
2011-05-21 11:34:15 +0100 fdlimit.c:665 [Debug] Transmission: SO_RCVBUF size is 65536