Utorrent tracker constantly updating
Say I'm using a tracker and the announce url changes (for instance a tracker that uses passkeys and the passkey changes).I have no way to update the 100 torrents I have seeding from the tracker. And if you're seeding a lot of torrents that'd get tedious.
It is not possible to update the tracker url for more than one torrent at a time.We’ll assume 25 peers are being sent back, because there are always small swarms, which won’t have enough peers for the default 50. In theory, every client should announce to this tracker as well, but the reality is a little different.So we’re looking at maybe another 260 bytes per response, or 7.2Mb/sec, taking the 30-day total to 18.6TB sent out, and ~25.8TB total. UDP ones are slightly different, since it uses a send-receive-send-receive pattern, but overall it works out to 114 bytes sent, and 186 bytes returned which at our loads means 3.1Mb/sec received and 5.1Mb/sec sent, giving 30-day totals of 8.2Tb received, and 13.4Tb sent (21.2Tb total) And of course, none of this takes into account overheads, which adds about 3% onto TCP traffic, and half as much for UDP traffic (a better example is here) It sounds a lot, and it is; and what’s more, most of it is preventable. See, not all clients support multiple trackers If we assume that it’s about 1% of all clients, that means that on tracker 2, you will find listed 99% of the peers that are on tracker 1.u T allows you to select all the torrents - save and then it updates all the torrents' announce urls. But you should not delete your system32 or "/" anyway. I would love to see a batch tracker editing feature, as manually going over every torrent is really messy, and time-consuming.For torrents with more than one announce url you could have the update field a textarea box that has each tracker on a new line. (If this suggestion exists, sorry, I tried searching for it.) If anyone have this "issue", you can always just move the affected .torrent files into a folder, and use Notepad on Windows. If not, you can cook up a small bash script using sed bash in like 5 minutes. For example: removing certain tracker URLs from a set of torrents would be really awesome. Content Wrapper:after.hidden.normal.grid_page.grid_page:before,.grid_page:after.grid_page:after.grid_page h3.grid_page h3 a.grid_page h3 a:hover.grid_pageh1.layout_2col_main.layout_2col_side.__live_spinner.__live_spinner .__live_spinner_indicator.__live_spinner .__live_spinner_indicator .
Error Banner a.modal_overlay.modal_overlay.hidden.modal_overlay .modal_fixed_close.modal_overlay .modal_fixed_close:before.modal_overlay .modal_fixed_close:before.modal_overlay .modal_fixed_close:before.modal_overlay .modal_fixed_close:hover:before.modal_overlay [email protected](max-width:630px).modal_overlay [email protected](max-width:630px).inline_editor_content:hover .inline_editor_edit.inline_editor_content .form_buttons.question_details .qtext_image_wrapper.question_details .qtext_image_placeholder.question_details .qtext_image.
Basically, If you’re connected to peers W, X, Y, and Z, and Peer W is connected to A, B, and C, you’ll tell W about X, Y, and Z, and W will tell you about A, B, and C.
It augments trackers, and means that even if there were two disparate swarms on a torrent (as can happen with DHT-only torrents, thanks to the incompatable Vuze and mainline systems), as soon as a single link is made (by a client that can handle both, for instance) the swarms start to intermingle. It’s not made any different to the primary tracker. Even more fun comes when you realise that any client that supports multiple trackers, tends to also support DHT, and so DOESN’T NEED multiple trackers anyway. If, however, someone on both groups had DHT running, then they’re going to become one swarm, thanks to PEX. But the question has to be asked, just WHY do people keep adding more trackers to a torrent?
That’s 2,777,800 bytes every second, or close to 2.8 megabytes (or 16.8 Mbit), each and every second, and that soon adds up.
2.8megabytes/second average works out to about 7.25 terabytes of data over 30 days. Then we get to the responses, which is when the tracker sends data back to the client.
The average bittorrent client updates to a tracker roughly every 30 minutes.