Stop abusing multitracker announces and improve the create torrent dialog to prevent misuse.
It's not too late to follow the specification! Announcing to multiple trackers causes unnecessary overhead and tracker load. DHT and PEX will tie swarms together, and following the spec kills many birds with one stone, including torrents and users who add too many torrents or break up load balanced tiers like here: http://forum.utorrent.com/viewtopic.php?pid=459762#p459762
By improving the create torrent dialog and adhering to the spec we make torrenting nicer for trackers and reduce unnecessary announces.
GTHK
shared this idea
19 comments
-
lostinlodos commented
Dead and nearly dead torrents are greatly helped by the current implementation.
Especially those that USED to be private.
Please DO NOT change this. -
Jeroenz0r commented
YES! many open trackers share the peers with other trackers already!
-
.dot
commented
@iycgtptyarvg
It is beyong stupid to globally disable DHT and PEX, those get automatically disabled anyways on a torrent to torrent basis if it is private flagged. -
paintball9
commented
if anything maybe a que system for trackers might be an option. making trackers wait a second while the previous ones finish updating. it would stop sudden loss of bandwidth when starting new torrents even if it does make the tracker updates last 5 or 6 seconds longer.
-
paintball9
commented
Not worth it. Private trackers ban dht so there goes your precious argument. if you are having trouble with too much traffic then maybe its time to cut back on the amount of torrents you are downloading at once. and start removing trackers that arn't working anyways. half the torrents out there include dead or missing trackers in their lists.
and just because you update one doesn't mean everyone is updating the same one. if you only update one tracker you are missing out on all the possible seeds and peers on the other trackers. just keep it like it is. it works great. don't fix it if it ain't broken.
-
Zerofire
commented
I know that some tracker Admin's do complain about load but that is because a client does not respect the minimum time between announces. µTorrent however does not contribute to this problem.
-
AdminSwiteck
(Admin, µTorrent)
commented
No, EACH tracker on separate tiers on EACH torrent is doing a separate update every 30 minutes.
-
iycgtptyarvg commented
@Switeck
Hmmm... I was not aware of that. I thought tracker updates occurred only once per 30 minutes or so?!?
In µTorrent's 'Tracker' tab it states: 'Update in xx:xx', where xx:xx is a time between 00:00 and 30:00 (for me). Are you saying that is not true? -
AdminSwiteck
(Admin, µTorrent)
commented
iycgtptyarvg, the problem with that occurs if you happen to have say 40 torrents with minimal peers and lots of seeds...that each have 30 trackers all on separate tiers. You're doing 1200 tracker updates probably every 30 minutes. On top of that, most of the trackers are either reporting the same ips...or reporting *DEAD* ips. Retrying all the ips (that are mostly seeds or dead/gone) on top of all the tracker updates can cut into uTorrent's ability to start new torrents as well as being absolutely nasty for marginal networking hardware and software.
-
GTHK, you are not going to like me, but I use www.torrentz.com, which has an option to add a whole bunch of trackers for each of their torrents.
As a matter of fact, I don't even download something if it has less than 5 trackers or so.DHT and PEX is permanently off for me, by the way. Private torrent sites don't allow them, and my router has trouble with DHT.
-
AdminSwiteck
(Admin, µTorrent)
commented
There are a few examples on the uTorrent forum where the current tracker handling *IS* causing torrent starting problems or maintaining peer/seed connections. Usually, this is because 100+ torrents are started with 10+ trackers all on separate tiers.
There *NEEDS* to be a low limit of how many trackers get retried at once per torrent! -
GTHK
commented
Except it DOESN'T.
-
.dot
commented
If following spec cripples a client, then it is crippled. Seems pretty obvious.
-
GTHK
commented
@TheChosenOne: Yes, let's make good behavior off by default, and give it an obscure and cryptic setting only the experts on the forum understand. This seems to be the µTorrent way as of late anyway.
@Aaron: That completely ignores 1) Some idiot mass adding a list of dozens of trackers 2) Badly made torrents 3) µTorrents bad behavior in multitracker announces, including the use of UDP trackers.
Any performance gains you think you're getting will a) Disappear after the first few announces b) Are being made more irrelevant with hole punching c) Stop having any gain after many trackers are used, and are only a burden on tracker ops from that point on and d) have no practical meaning on large torrents. The important thing here is to keep people with no idea what they are doing from doing more harm then good (and stop µTorrents own poor behavior). One user behaving isn't going to magically have a good impact.
@Napsterbater: Azureus wasn't crippling itself, it was following the specification instead of behaving in an obnoxious manner.
-
Napsterbater
commented
I love the way utorrent announces and it makes sense, Trackers with the same databases are in group so only one of those is chosen but trackers with different databases are checked for more peer/seeds, azures cripples it self only announcing to one tracker especially if that tracker has few peers/seed for what ever reason.
-
Aaron commented
I don't see the upside of this request in terms of uTorrent client performance. If you don't like that a torrent has several trackers then delete them manually (right-click -> Remove Tracker).
-
TheChosenOne
commented
I agree with the admin; this is something that should not be implemented. If it becomes implemented have it turned off by default.
-
GTHK
commented
Ok, why does that matter? You can only connect to so many peers before it becomes more then pointless. Things seem to be working just fine here with torrents stripped to one tracker. I can't see announcing to a list of >100 trackers as ever being useful (I recall one user attempting such a think), or even 6 which is what I commonly see.
-
AdminGreg Hazel (Admin, µTorrent) commented
Users complain to other client authors that uTorrent finds peers faster than their client, and this is usually the cause.
I would hesitate to cripple uTorrent just to follow a spec of questionable value, when no tracker admin is complaining about load.
