So now upload performance has dropped and has a range is 20 Mbit/s - 70 Mbit/s. Those trackers are showing as Error: Offline (No data received) or Error: Failed (Connection timed out: connect). In the last few months, in spite of new torrents on RARBG containing usually only their own Trackers. I have seen BiglyBT reach upload speeds over 250 Mbit/s upload, though more typical is 120-160 Mbit/s. Oh and give you an idea of how much I am seeding and queue settings: But it still tells me to increase the concurrency. Notice I didn't go all the way down to 25, I used 128, down from the 1024 before. Tried the numbers you suggested, here is what it looks like: (Along with not scraping inactive torrents.) My stats graphs always look about like Ok, I am getting this again. Personally, I use 15 seconds for the connect timeout, 35s for the read timeout, and a concurrency of 25. Short timeouts ensure that busy trackers or ones that are having network connectivity issues can be treated the same as offline trackers, and passed over in favor of more responsive ones. The whole point of having multiple trackers for each torrent is that connecting to any one of them is unimportant - there's always the next one on the list. I'd probably drop that way, way down - if a tracker isn't able to respond to a connection attempt within a few seconds, even if the connection would eventually succeed, it's probably so overloaded (or having other issues) that you're better off just bailing on it and moving to the next one in the list. With that kind of window, every attempt to contact an unresponsive tracker is going to potentially delay a subsequent connection to a working tracker by up to 120 seconds. "Manage tracker activation to reduce load" could also possibly help (though I don't know if that will affect scraping at all).Īlso possibly related: Two minutes is an incredibly long connect timeout. If you have a significant number of inactive torrents (and it seems you do, specifically all of the torrents in various "Queued" states), there's not a lot of value to scraping them all. Stick to 3 trackers max, no more than that is needed, having 500 trackers wont make a difference, and you’ll be responsible for negatively affecting tracker’s servers performance.Īnd before people start ranting “oh but I added 100 trackers and my speeds increased! how u explain that?!?!?” Simple, one of the trackers connected a peer to you, which by chance had a nice upload speed, that very same peer could have connected to you by DHT, or even by one of the trackers that you already had.I'd probably start with turning off "Scrape torrents that aren't running", personally. OK people, time to clear things out, being a good or bad tracker does not depend on speeds, a tracker is a simple middle man responsible for letting know how many peers a torrent has, the DL/UP speeds will depend ONLY on YOUR DL/UL speed and the other person’s DL/UL speed, the tracker has nothing to do with speeds.Īnd please, stop adding a shit load of trackers, there is something called DHT, which basically turn trackers useless, peers are able to connect to each other without the help of the middle man (tracker), besides, if everyone adds a shitload of trackers, they (the trackers) will be hogged, and that will affect their server’s performance. If you have more working public torrent trackers that do function properly, feel free to suggest them in the comments. The rarbg tracker seems to have multiple mirrors, such as udp://10.:80/announce and udp://11.:80/announce so you might try out these as well to see if they are working. Update, March 3rd: I added some new trackers and removed some non working ones as per the comments and feedback I received. New version available! Check out the updated 2016 torrent tracker list!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |