Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Khurram

macrumors 6502
Original poster
Aug 28, 2006
332
0
So I just installed trasmission...
It seems that when I open a torrent it takes forever to start linking to seeders and start downloading (i'm talking like 20 minutes).
I opened the same torrent in azerus and it started connecting and downloading almost instantly.
It's doing this with all my torrents.

Any idea what could be wrong? I tried port forwarding but no luck..
Thanks in advance for any help
 
Yeah i'm getting the same problem here, i tried uninstalling it and reinstalling it and it still sat there, but work right off the bat with Azureus.
And when ever i see someone talking about it they always say how great it is,
Still don't know why they do.
 
Connects instantly for me... and thats on my 64kbit/sec connection lol.

BTW, I'm using version 1.11 and Leopard 10.5.2, if this helps.

Try trashing the support/preferences files and see what happens
 
Same here (no problems with waiting on the beginnning), on a 120 kbps line :D
 
Same here but I can wait... I'm a patient man. However, Transmission was good but now it pisses me off as it's really erratic, it would go at a 300k (with like 5 downloads) and it will drop down to a 0k every 5 minutes.

A 500mb torrent with 300 seeders took me about 3 days to download and my download connection is pretty damn fast. Also I find that every time I open the Transmission window, connections start slowing. It's a little weird but I'll stick with Transmission till they fix this but I'm tempted to go with another torrent client (helps the fact that I have like 7 incomplete files because of this =P).
 
Remember that the TCP port you need to forward is different for Transmission than for other BT clients.

Transmission by default requires TCP 51413 to be forwarded rather than the usual BitTorrent range of TCP 6881-6889. You can change the TCP port in the advanced section of the Transmission preferences to 6881 if you like, which may help. However, considering how much crap out there now tries to connect to that port level you really should reconfigure your port forwarding and leave Transmission as it is.

BTW, I get absolutely no delay in connecting when at home, but suffer the symptoms you describe when on the wifi network in the office where the port forwarding isn't configured. I'd guess that is the most likely culprit for what you are getting, unless of course your ISP has started traffic shaping.
 
hmm good point but I have been using Transmission at this location for about 4 months and the symptoms started occurring about last week ago or so ><

I don't think I installed a program that might share the port. Can you explain more about traffic shaping?

Thanks,
KJ
 
It's probably best if you read the Wiki summary rather than me try and explain because I have a tendency to go into technobabble ;)

Link

Basically if too many users with an ISP try and BitTorrent at once it can cause performance issues for other users attempting to stream video, make Skype calls etc., so the ISP will give the BitTorrent stuff lower priority on their network to avoid it hogging all the bandwidth.
 
It's probably best if you read the Wiki summary rather than me try and explain because I have a tendency to go into technobabble ;)

Link

Basically if too many users with an ISP try and BitTorrent at once it can cause performance issues for other users attempting to stream video, make Skype calls etc., so the ISP will give the BitTorrent stuff lower priority on their network to avoid it hogging all the bandwidth.

Hmm I don't think my ISP does that since I looked on the list and it wasn't on the list =D. Plus I have been using for around 4 months =D

Btw I think I found the problem after endless searching ><

http://forum.transmissionbt.com/viewtopic.php?t=2797&postdays=0&postorder=asc&start=45

xenedar said:
Done all of that.

The problem is with Transmission's scrape and announce.

Looking in the Tracker tab (a useful addition which has proven very revealing with this issue), the time to announce and time to scrape count down. As soon as any of the timers get down to zero, all torrents drop off to zero k/sec. Approximately 60 seconds later, transfers come back and resume until a timer in any torrent gets down to zero. This occurs regardless of whether the torrent is paused or running/waiting (scrape/announce occurs for paused torrents), which means that the fewer torrents you queue, the better your chances, since it is entirely conceivable that you will end up in scrape/announce hell with timers hitting zero every few minutes or so. The issue can also be immediately triggered by choosing "Update Tracker" from the Transfers menu (if it is available).

During the times of normal activity, Transmission performs like a champ. I'm on 512/128 and was getting 50KB/sec. But with an interruption every now and then during scrape/announce. Other applications on my computer are not affected. Indeed to the contrary; when a scrape/announce occurs, my browser suddenly becomes very speedy as torrent speeds plummet, until 60 seconds(ish) later when normal Transmission activity resumes.

My observation is that it is most prevalent, and exceedingly replicatable, with torrents tracked by PirateBay trackers, such as open.tracker.thepiratebay.org (eg: eztv), to the point where, if possible, I will choose a torrent NOT tracked by thepiratebay.org over one that IS. With torrents off other trackers, such as some private ones, in many cases I have not had an issue. Certainly this suggests that something funny is going on with these trackers (being slow to respond or something), but Transmission is handling it badly, since this does not seem to affect other clients such as Azureus.

With such torrents, it is not unusual to have to wait 5 minutes before starting to get any kind of transfers happening, as Transmission announces, hangs, scrapes, hangs... even longer if it needs to fall over to another tracker (again, eg: eztv torrents often list 5-6 trackers).
 
Interesting comments.
I don't think my ISP is traffic shaping because as I said, it works fine on any other torrent program.

I'll try to trash preferences and set it up again and see what happens.
Good to know i'm not the only one experiencing this.
 
Interesting comments.
I don't think my ISP is traffic shaping because as I said, it works fine on any other torrent program.

I'll try to trash preferences and set it up again and see what happens.
Good to know i'm not the only one experiencing this.

Meh I moved over to Azureus for now until Transmission fixes this crap, my torrent went from estimate of 2 days to 6 hours.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.