torrents are very fickle things. this happens all the time to me, and the only solution i can come to is that some trackers just dont work as well, and/or they somehow limit people to a ratio'd download rate. Some of the slower ones i have been on will go really slow when the upload is limited to 5kb/s then speed up when i limit it to 25kb/s. Most annoying thing really is that its always the largest torrents that go slow!
its just strange that some torrents will happily top out my 2mb connection without me doing any uploading (regardless of wot my upload limit is set at). then others will just not do anything regardless.
U got Service pack 2 on yer new machine? If so it a common problem. Microsoft limited the amount of tcp/ip connections down to 10 or something.....u need a patch to increase this. Search on google for "TCP/IP xp patch"
Before you install said patch, i'd reccommend looking at this: http://www.neowin.net/forum/index.php?showtopic=267665
The best way to get the most out of a BitTorrent client is by managing the upload speeds, as said above. My tips for the top: Use NetLimiter 1.30 to limit the upload speed of the client slightly (eg if you have an upload speed of 256kb/s limit the speed to ~22/24kB/s). This helps speed up other internet applications (eg browsers) by allowing them to send requests too, and speeds up the client slightly by other applications not having to send their requests repeatedly. Files with high seeders/leechers (eg 10+): Limit the local upload speed on the torrent to 3kB/s to allow other torrents more bandwidth. Files with low seeders/high leechers (eg 2 seeders/10 leechers): Limit the local upload speed to about a third of your available bandwidth (eg 8 kB/s if you've limited the client to 24kB/s) Files with low seeders/low leechers (eg 1 seeder/1 leecher): Check the #seed/#peer details - if the seeder(s) is connectable (not choked) limit to a third, if the seeder is constantly choked limit to 3kB/s. Also check that the leecher is giving you pieces too, if not limit to 3kB/s. The above is assuming that you have 4 to 10 torrents on the go at once. For torrents with low seeders your upload rate does affect your download rate. If you're seeding a torrent with low seeders and low leechers whack the upload limit up to a third. But remember you're still supposed to share so keep the torrents open after completing until your ratio is at least 1:1. People that snatch and run are scum, and they're usually the ones to whinge on about slow downloads - if they seeded too the downloads wouldn't be fucking slow in the first place.
Ive spent a fair while reading about this, with mixed results, but the general idea I get is that this doesn't improve the speed of your connections (just what i've read, can't verify this....apparently it's coincidence if speeds increase), but does increase the amount of search requests possible. It only limits INCOMPLETE connections PER SECOND, and therefore is said not to increase download speed. Also - the better P2P programs such as eMule have already adapted to deal with this limitation. As far as I can see though there is not that great a security threat. Microsoft say it is to prevent the spread of viruses, but this is going to be a seemingly negligible reduction, and have little impact if people continue to go unpatched and not use any anti virus/firewall software. Still - I think I wil wait and see what you lot say before I install it I would reccommend actually doing a bit of background reading first though and not jumping in until to understand what the implications are of installing the patch and why there is such a limit there in the first place.
the golden rule of all things related to computers. The only way people get knowledgable about wot they are doing is purely from reading availiable sources usually via a google search. some people who dont know anything about computers seem to think that we just automatically know all this stuff. but now whenever my mates ask me to help them i just send them to google and since ive been doing that they can now all sort their own problems
The limit is supposedly there to help stop the spread of worms etc. Not much good though, as with a limit at 10, within a minute 10^60 (10 with 60 zero's trailing) machines could be infected... The only thing I'd say about the patch is to backup tcpip.sys before applying it - and apply it you should.
First of all get rid of Bitcomet and use Azureus, ive tried bitcomet and not all trackers support it, probably a reason why!
That's how I got so knowledgeable - t'was my addiction to pornography @ others - Azureus is canny resource heavy - I prefer ABC (version 2.6.9 though - don't think of getting the newly released version 3.0, it's buggy to fuck )
I wouldn't bother with it, as my IP will be on the logs of almost every tracker out there (including the one where I'm a senior uploader... ), so it's a tad pointless. Good idea in theory though.
lol good call!!! u can stop sending data to the "blacklisted" ip's....but you cant stop em getting logs from the tracker. hmm...never thought of that :laugh: back to ABC it is
Not a lot of peeps realise that like - a good example is LokiTorrent, if you ever used it your IP and all the files you downloaded are in the hands of the MPAA... I'm a criminal. If you wanna keep your details away from the law, then use a tracker/site in a country that doesn't recognise copyright laws (eg www.thepiratebay.org), or use a private tracker (look below ).
