New Torrents Start Seeding Delayed
-
Well Uwe I use this thread whose title seems adequate.
I notice a slightly different problem.OS Linux Ubuntu 10.04 64
Client Transmission 1.93 (10621)When I seed a new torrent I always observe a big time gap between the moment when the site gets aware of the presence of a single leecher and the moment when the tracker starts the file transfer. In other words I get the feeling the tracker lags a lot in getting aware of the leechers as long as they aren't at least two.
-
Sorry, I've split this into an own topic, because it is about a similar but different subject.
What you observe is related to the way the updates between torrent client, tracker and site works.
a/ There is delay of a few minutes ( ~1 to 3 min) between the tracker and the result shown on the site. You can test that out by starting a torrent and look for the delay between seeing it seeding with 0 (1) peers and "working" tracker status in the torrent client and it appearing in the search result on the site.
b/ When a new torrent has been uploaded and started to be seed, the torrent client will update the tracker and the torrent will become visible in the "Browse" and "Search" pages (see a/). At that moment there are not yet any leecher. So no immediate upload.
Leecher joining the torrent's swarm will be registered by the tracker and visible in the count on the site. However, the next update between torrent client and tracker is programmed to be in 30 minutes (a tracker cycle, usually you can see the count down for that in the torrent client programme somewhere) and until that update, the initial uploader torrent client does not know these leecher.
That means in practice, the seeding will start transferring data only about 30 minutes after the torrent has been improved.
The update cycle can be broken by either force a tracker update manually in the torrent client programme or by a STOP and restart of the torrent in the torrent client programme. The restart will do an update.
-
NP. Thank you.Very clear. Trying someway casually I had already come to understand the possibility of forcing the manual tracking update which, in my personal experience, worked quickly only with at least two leechers. Nothing to be worried about I'd say though.
A negligible, at least in my case, bandwidth waste
