Are torrents supposed to make your internet slow?

shazam

Newcomer
Whenever i have torrents running on utorrent, the torrents work fine but everthing else is WAY slooooow. I can barely brows the internet when utorrent is running. Is this supposed to happen? I thought bit torrents were supposed to save bandwidth, not eat it all up? Am i doing something wrong?
 
Whenever i have torrents running on utorrent, the torrents work fine but everthing else is WAY slooooow. I can barely brows the internet when utorrent is running. Is this supposed to happen? I thought bit torrents were supposed to save bandwidth, not eat it all up? Am i doing something wrong?

Well a torrent with a lot of seeds is going to use up a lot of your bandwidth unless you set it. Depending on the client you should be able to set the amount of data you can receive through it, this will open up more of your bandwidth for browsing, but at the same time it is going to slow your download.

Keep in mind I'm far from a torrent expert, and I've never used utorrent.
 
Ripped off from somewhere ages ago and saved because it was both somewhat techy and eloquent:
When your PC opens a TCP connection to or from a remote server, your PC tells the remote server what your PC's TCP Receive Window (RWIN) is. The basic flow control mechanism of TCP is that the sender will stop sending data if it has not yet received a TCP acknowledgment (ACK) for any of the last RWIN bytes of data sent, and the receiver should transmit an ACK packet back to the sender when there is about half an RWIN's worth of data received but not yet ACKed. The sender uses the arrival of the ACK packet to pace itself on how fast to send data to the receiver. Pulling in a fast download requires not only the download packets to arrive quickly, but also for the ACK packets to get back to the sender in a timely fashion.

If you saturate your upload, the ACK packets of your downloads (also including simultaneous web surfing, which tend to be many requests) will have to queue up waiting for a gap between the congested upload data packets. So your ACKs will be delayed getting back to the remote download server, and it will therefore believe you are on a very slow link, and slow down the transmission of further data to you.
In conclusion: Limit your upload speed to ~80% of the theoretical maximum and experiment from there. Leave the download rate uncapped.
 
Limit your upload speed to ~80% of the theoretical maximum and experiment from there. Leave the download rate uncapped.
Yup. And if someone is gaming you're sharing the connection with I've found that keeping the up under 50% keeps 'em from bitching about ping too much. ;)

It sounds weird, but throttling your up speed can dramatically increase your download speeds as well. Give it a try. :)
 
Weird? I thought my ripped of quote explained why perfectly well. Oh wait, you didn't read that, did you...? ;) :devilish:

Big words and full sentence structures confuse Digi... ;)
 
In most cases, I've found its not actually the bandwidth of torrrents at blame for slow intolerable bandwidth but port usage of torrents. Basically, torrents use a ton of ports which on standard routers causes a lot of actual performance issues for redirecting due to the port amount being more than the size of router port table resulting in constant thrashing of the table.

As a result, installing a new firmware like DD-WRT then increasing the port table size to 1024 or larger results in a huge improvement with much reduced CPU usage on your router (with a table size of 512 my internet becomes unusable while with a table size of 1024 I don't really notice it much).
 
In most cases, I've found its not actually the bandwidth of torrrents at blame for slow intolerable bandwidth but port usage of torrents. Basically, torrents use a ton of ports which on standard routers causes a lot of actual performance issues for redirecting due to the port amount being more than the size of router port table resulting in constant thrashing of the table.

As a result, installing a new firmware like DD-WRT then increasing the port table size to 1024 or larger results in a huge improvement with much reduced CPU usage on your router (with a table size of 512 my internet becomes unusable while i have no idea how to do that.
 
Ripped off from somewhere ages ago and saved because it was both somewhat techy and eloquent:

In conclusion: Limit your upload speed to ~80% of the theoretical maximum and experiment from there. Leave the download rate uncapped.
Glad to finally read an explanation of why upload speeds in p2p should be capped!
 
He might have said port, but think of it from a connection standpoint. To you it's one port, to the router is hundreds or thousands of connections.

You may have 1 port open on your PC, but to your router, it has to deal with all the CONNECTIONS torrents uses. That could be hundreds of active connections, plus hundreds of new connections, plus hundreds of old connections going through the time-out and close phases.
 
Yea but from what I understand an IP port and a connection are two different things and the terms are not interchangeable. I'm not a networking expert by any means hehe but that's what I've been told anyway..

So if you say port when oyu mena conneciton it can lead to some confuson wouldn't you say? :cool:
Peace.
 
Are you running vista? If so it might not be even be related to uTorrent.
Recently it has been buzzing around the web of problems related to severe drops in network performance down to ~10, 15% just by having an mp3 playing, im not aware if it's just related to mp3 playback or any kind of audio format, things appear to point down to vista DRM scheme being defective by design. M$ is pretending to be nothing severe about it.

http://it.slashdot.org/it/07/08/26/1628200.shtml
 
In most cases, I've found its not actually the bandwidth of torrrents at blame for slow intolerable bandwidth but port usage of torrents. Basically, torrents use a ton of ports which on standard routers causes a lot of actual performance issues for redirecting due to the port amount being more than the size of router port table resulting in constant thrashing of the table.

Torrent programs use often only a single port but has multiple connections established to that port with inbound and outbound data. What could cause some perfoamcne issue is if there is a large amount of connections and AV/FW is checking the data for malware (depends on software or HW for perfoming these tasks). Also if the data traffic is encrypted between host and client then that could affect the perfomance noticably especially with many connections.
 
The only solution is to buy the most expensive internet service available. If you can't find a service that's really expensive, move to a new city where internet service is more expensive.
 
You also need to use a hack to turn up your max half-open connections. The limit in XP SP2 and Vista is a whole 10 of them at once, and P2P apps love to open them up. If you run two P2P apps at once, you absolutely will go past this limit and it causes your internet connection to become very laggy.

This guy made a util to tweak the setting for XP 32-bit.
http://www.lvllord.de/?lang=en&url=downloads

There are also ways to do it with XP x64 and the Vistas, but I don't know of good links offhand.
 
It could be ay of the above, and I've also seen wireless routers that simply won't cope with te number of conections. They get flooded and in some cases just plain die. I have 3 wireless routers here and the only one that doesn't die if I run bittorrent for extended periods is the one running DD-WRT. And I had to tweak the initial setup on that to make it behave reasonably.

Cappng the number of conections and capping your upload bandwidth can get you to a usable system. With DD-WRT I increased the maximum number of connections the router will allow, decreased the time out on those connections and set Bittorrent packets as bulk traffic, and that finally resolved all my issues. My network now behaves extremly weel with or without bittorrent running.
 
It could be ay of the above, and I've also seen wireless routers that simply won't cope with te number of conections. They get flooded and in some cases just plain die. I have 3 wireless routers here and the only one that doesn't die if I run bittorrent for extended periods is the one running DD-WRT. And I had to tweak the initial setup on that to make it behave reasonably.

Cappng the number of conections and capping your upload bandwidth can get you to a usable system. With DD-WRT I increased the maximum number of connections the router will allow, decreased the time out on those connections and set Bittorrent packets as bulk traffic, and that finally resolved all my issues. My network now behaves extremly weel with or without bittorrent running.

That's true too. I don't know if there are any consumer-level routers out there that can survive a bittorrent connection surge for long. Usually they will slowly bog down and may just freeze up completely. Some are much worse than others.

There are some 3rd party router firmwares for the Broadcom-driven G routers out there that fix up a lot of bugs in the OEM firmware. DDWRT is one I really like.

Also worthy of note is that if you are on a cable modem, some of the old ones have major problems with lots of connections or how fast you open a number of connections. Especially older Motorola Surfboard modems (4x00) from years back. They will totally freeze up and you have to power cycle them to get your connection back. I was stuck with one of those for a while and had to get it swapped out.
 
I find limiting upload speed to 60k works for me, but obviously this would be a function of how fast your maximum upload speed is. But, yes, I certainly find that upload speed on my torrent client (somewhat counter-intuitively) can play a major role in how generally responsive my overall web browsing experience is.

And the Holy Grail for setting up your router correctly for Port Forwarding: http://www.portforward.com/english/applications/port_forwarding/Utor/Utorindex.htm
 
Back
Top