Transmission 1.83 on Ubuntu: massive network slowdown

[Cubytus]

Hi to all,

I don't know if this a bug or misconfiguration somewhere in the network devices chain, but running Transmission 1.83 on a network whose gateway is a Tomato/MLPPP 1.19mp2-based router slows the entire network to a crawl.

I configured Transmission to use only 100 max. connections, de-activated PEX and DHT, yet running it only leaves a few kB/s for other computers. Why I'm posting it there is 6 times as much connections held by aMule with a large number of downloads doesn't slow anything down.

Is there any particular info I could give to help isolate the issue?

Thanks for help,

[Cubytus]

It's already "braked" at 250kB/s all day long in down, 50kB/s up (45 to 55% of available bandwidth, depending on the time of the day), and even without the "brake", it's still running at around 20KB/s, up and down. In fact, the real-time bandwidth graph in Tomato/MLPPP shows averages of 22 to 23 kB/s, where Transmission is the only non-daemon running. In comparison, a full-speed transfer reaches 550kB/s up, and uploading stabilizes at around 96kB/s.

Still, it seems there's plenty of available capacity, yet something seems not to be workign as expected.

[teeedubb]

im having the same issues. transmission 1.92 on ubuntu 10.04. have tried all the measures here. im using a billion 7800n router. the funny thing is that im unable to connect to my router with my desktop (torrents download on a separate server) so it even affects local traffic....which is strange coz my router/entire setup is gigabit. have never had issues like this with other clients. doesnt say much for transmission when it fails its most basic task ( and those fixes mentioned are ridiculous.... theyre like telling people to just drive slowly on a flat tyre instead of getting to the core of the problem and fixing the tyre)

how did a trashy piece of software like transmission become the default client for ubuntu? which one of the developers is sleeping with shuttleworth??

[Jordan]

(Moving to the general support forum)

[rlinsurf]

Ok, no need to defend Transmission. I never use anything else.

But is there a solution? I posted in another thread that all my Internet services go down -- not just slow, but out -- when Tramsmission 1.92 is up, and only come back when I have quit the app. This is happening even when TR is showing 0.0k for all uploads/downloads, and I have plenty of bandwidth in any case.

It was suggested that I disable DHT and keep my peers under 100. I did, to absolutely no effect.

This is Mac OSX 10.6.3. Anyone know what's going on here?

[rlinsurf]

Ok, I have further to this. This all seems to have been triggered by a single torrent. Once it was downloaded, and I removed it, all internet services returned pretty much immediately. If any of the Transmission Team would like to see the .torrent, please PM me to upload it to you.

PS, as this is happening under Mac OS X, and because there have been reports of single files creating havoc with Mac users networks, with similar symptoms, I will also be posting this report here:

http://forum.transmissionbt.com/viewtop ... f=4&t=9686

[Terseus]

I also suffer this... ¿bug? I will try to explain my case deeply as possible, please excuse me for my poor english.

I have transmission 1.92-1 with only one torrent right now, but it have a lot of peer/seeders (+300), the limits are set to 60 peers per torrent / 240 peers global and download/upload speed limit to a ~60% of my network speed.
When run it there are no problem, transmission start to get peers pretty quick, but at a given time it begins to loose peers and I can't make any connection to a external host (tried with Firefox, APT, and nmap) but I can connect to a LAN network with no problems, what makes me think it can be a "connections limit" of my router (a crappy cable-router from my ISP); this doesn't happen me with earlier versions of transmission (tried with 1.22-1, stable Debian repo).

I have seen that transmission 1.22-1 make a maximum of 100-120 tcp connections at the same time but no more that this, and 1.92-1 can up to 380 connections before it begin to loose peers, after a while it recovers them an then stabilizes to 100-120 connections and work again.

It seems (but I'm not completely sure) that adjusting the transmission config parameter open-file-limit from 32 to 8 help a bit, but not much.

I don't think this is a transmission bug, it seems to be just too much aggresive opening connections, a config parameter to limit the maximum of concurrent connections would help to people who have (like me) a crappy router that can't handle the transmission massive connections when get new peers.

If a developer can point me to where in the source must I change to limit the maximum of concurrent connections, or post a patch what do it, I will test it and post the result.

Thanks for your time and patience ^_^

[Terseus]

Sorry x190, I don't mean to limit the peers but concurrent connections, the same config (peers 240 global / 60 per torrent) works fine in transmission 1.22 but not in 1.92, that's what I was pointing to.

Is there a way to limit the maximum concurrent connections? I guess this will make the peers search slower but I don't care about it, I just want transmission don't blow up my router/connection/kernel/whatever the bottleneck is.