Too many Torrents: Try limiting the number of active torrents and queue the rest. Anything over 6-8 active torrents is overkill and will hurt overall speeds (and tax your processor and hard drive).
This is commonly the cause of a whole Internet connection being slower, but it also often causes BitTorrent downloads to be slow (sometimes even when the Internet connection, for other uses, is reasonably fast).
I have a strange issue. I am not a big file sharer, but have some files I want to recieve with bittorrent. I notice bittorrent is extremly slow on my archlinux maschine. If I boot into knoppix, it is quite fast, and so is ubuntu live cd. While a download of a file lasts 4 days if I use arch, ubuntu and knoppix will do the job in 3 hours. Arch recieves 2-3 peers, the other systems hundreds. It does not depend that much on daytime or weekday, as this happens everytime I try it out. So what is the trick? As it is a behaviour on the same machine, in the same network, it must be a missconfiguration inside my archlinux setup. I have no idea.
I would guess that both ubuntu live and knoppix have quite sophisticated iptables setups (kind of necessary for a live cd) which would allow outgoing and related incoming packets on any ports you want to use.
The big difference is that you don't have ANY software firewall in arch, so if you install iptables and forward whatever ports your client uses (normally 6881-6999 as slackhack says) I bet you'll see much faster speeds.
one place even said 240kbps bitrates were common with a proper configuration. i haven't used bittorrent a lot, but the highest i remember ever getting with arch is around 50-75kb, and that was surprising. most often it's in the 15-25kb range for a "good" torrent, and now even that is starting to sound too slow in comparison.
tonight or tomorrow i'll install bt on my laptop (slackware) and see what happens. i guess i could try knoppix there too. i have the same setup as Moo with all my computers behind a firewall and no individual firewalls, so it will be interesting to see if i get higher speeds w/the other two distros. i'm using the knoppix 4 dvd torrent from the link on as a test -- right now i'm getting 1.8kbps with 29 seeds and 16 peers, so that is pretty pathetic.
i just set up bittorrent on my webserver ( :shock: ), forwarded the ports there, and it's not going any faster than arch (that's on debian, btw). if anything, it's a little slower, with about 30kbps right now compared to around 46 that arch got up to. (okay i just checked again, and it's at 39-40, so maybe it will just take a few more minutes to get up to its stable speed). the debian client doesn't tell you how many peers and seeds, either.
I use ctorrent and rtorrent. ctorrent is useless. rtorrent is slow, 10k is what i get on an exceptionally clear day. azureus is a bit slower than that. Right now I am getting 1.78k coming down the ADSL pipe. Some time back I checked speeds with 2 boxen side by side sucking the same file, one was on a 56k modem, the other adsl, both running Arch and azureus with the same settings. The result ? the 56k line was twice as fast as the adsl line. That was an extended test, not a snapshot it ran all afternoon and the dialup was at capacity all the time. So? i doubt if it is a firewall problem. I blamed the ISP, perhaps it is something to do with network or ethernet? My question then is why ethernet should perform so poorly while ppp works so well??
yes - I've also heard that many ISPs are throttling the 'normal' BT port range. May be worth using a higher port and seeing if that makes a difference. I use the stock arch bittorrent client and I regularly get speeds around 100kbps on well-seeded torrents.
Tried that torrent as well and it started with 50K went up to 90 within 10 seconds and after about five minutes it's running around 350K which is almost the maximum for my connection. I had similar problems as you for quite a while though: Download speeds rarely went above 10K but I never figured out what was wrong, I just stopped trying to download stuff with Bittorrent and when I tried half a year or so later it was working well again.
For anyone getting slow speeds, and assuming your ports are set up correctly, have you limited the amount of upload that your client can use? If you don't do this, bittorrent will swamp your upload, and this will have a corresponding effect on your download. 75-80% of upload is generally recommended.
i get that, thanks, but i never thought about it before having more than one computer. for example, say a network has 100 computers on it, 192.168.0.100 - .199. port 6881 is forwarded for 192.168.0.100. that means only one computer on the network can use bittorrent and none of the others can? no, but why not? i don't get the reasoning of forwarding a port to a particular computer if the other computers can use it anyway. :?:
about the speed issue, on further testing i think we're all being too paranoid. last night i tried the knoppix download again, and after 5-10 minutes i started getting speeds close to 350kpbs. so i think it must just be a question of the particular torrent being slow at any particular time, or some other external factor. the fact that Moo got 450 also seems to suggest that it's nothing specifically to do with arch (to me, anyway, although not knowing much about BT i could be totally wrong ).
I noticed that sometimes, for a limited period of time, I do get the highest speed. Checking the peers tab for this torrent, I can see that when that happens, I'm downloading at full speed from just one peer. And as soon this peer disconnects (or whatever) the download speed gets back to 5-10 kB/s. Other peers speed download seems normal, many peers download at very high speeds.
Because of the very nature of BitTorrent, speeds are not guaranteed for any given torrent swarm. While you may get great speeds in one swarm, you might not in another. This is due to the fact that BitTorrent is a P2P protocol, so it depends on the upload speeds of the other peers you are connected to to generate your download speeds. A common misconception held by many people is that torrent swarms that contain more seeds and peers are faster than those with less. This is not always the case. There can be a swarm with only a few seeds and/or peers on fast Internet connections, and you'll be able to get great speeds from them, while a swarm with many more seeds and/or peers might contain mostly people with slow, dial-up Internet connections, will get you terrible speeds from them. In the same vein, connecting to more seeds and/or peers does not equate to greater speeds, and seeds don't necessarily give better speeds than normal peers.
As I said, other peers speed download seems normal, many peers downloading at very high speeds. It makes me wonder why I can only find one or two peers willing to upload, while others can find so many so easily.
I have website blocking enabled in Malewarebytes, as a result i keep getting notifications about blocked IP's while downloading torrents using Vuze client and i keep adding them to the ignore list. Download speed already feels a bit slower, but i can't tell for sure, maybe it's just placebo effect ..
The only time MBAM might have an effect on download speeds would be if it blocks connections to some peers/nodes, which it will sometimes do since many of them frequently reside on known malware-friendly IP addresses and ranges that we block.
I am running version 6.11.2 on asrock J4105 with 2 sata ssd as a cache pool and 3 HDDs, linuxserver.io qbittorrent with gigabit internet connection. Download location is set to cache pool. Unfortunately all downloads cannot exceed 40 - 50 MB/s speed and CPU utilization reaches up to 100% followed with warnings "CPU_IOWAIT".
I guess this point is crucial... When a large file is moved from array to cache pool the transfer speed is quite low (around 60 - 80 MB/s), the speed is far more faster when the same file is being moved from cache pool to array (130 - 180 MB/s). Strange is it?
You might already know how to find and download torrent files by loading them into a client such as uTorrent. uTorrent is one of many popular torrenting clients, but despite its reliability, its download speeds can sometimes seem pretty slow. Fortunately, there are a few tricks available to make uTorrent faster, and these tricks often apply to other clients as well. There are a variety of factors that may affect uTorrent's download speed, and this wikiHow article will guide you in making your uTorrent client faster than ever!
If you're using the PIA app and are experiencing slow speeds when connected, we recommend that you first try to change the ports that your application is connecting to. For more information on how to change the ports, your application is using please review this article. We also have some recommendations for gamers here.
Your ISP-rated connection speed is based on connections to the ISP network under ideal conditions. However, VPN connections incur additional overhead due to the encryption process; using higher levels of encryption would slow the connection even more. This can certainly be further reduced by connecting to gateways that have additional routing latency or have a lot of traffic on them at the time. Additionally, some ISPs do restrict certain ports, which is why we recommend using the connection issues article as stated above.
By its very nature, internet technology has many factors that can impact the speed of an internet connection, and as such, the speeds you see can be affected in many ways. Windows in particular will not see more than 150 Mbps at most due to the TAP adapter bottleneck. This isn't specific to our application but to the OpenVPN protocol on Windows in general. If you're seeing less than the expected value (as outlined above), our support team is more than happy to work with you to troubleshoot the reduction in speeds you're seeing. To assist our team in identifying the cause of these issues, we'll need the following information from you:
760c119bf3