Save Upload Queue Waiting Time

From EMule Wiki
(Difference between revisions)
Jump to: navigation, search
(remove unused caracters)
 
Line 19: Line 19:
 
SUQWT saves each upload queue client's wait time when it exits the upload queue and restore it the next time the client comes back in the queue. You can take advantage of this feature only if the clients your are downloading from have activated SUQWT.  
 
SUQWT saves each upload queue client's wait time when it exits the upload queue and restore it the next time the client comes back in the queue. You can take advantage of this feature only if the clients your are downloading from have activated SUQWT.  
  
[[category:features]][[Category:stullemulefeatures]][[Category:Morphxtfeatures]]
+
[[Category:Features]][[Category:StulleMule features]][[Category:MorphXT features]]

Latest revision as of 22:11, 6 May 2010

Basically, Save Upload Queue Waiting time allows one to carry wait time from previous dead-end upload queue waiting sessions over to the next upload queue sessions until one manages to get through the upload queue, somewhat like holding a spot in a waiting line by using your gym bag or other article - if you're not there, the bag stays there and people move around it. (in an ideal civilized world anyway)

Abbreviation: SUQWT

see: http://pages.infinit.net/moonligh/eMule/SUQWT.html


Save Upload Queue Wait Time (SUQWT)

Ever tried to get some rare files using eMule only to see sources quit on you after waiting for days to get from #6000 to #500? Well, with SUQWT, this is not going to be as much of a problem anymore. How does SUQWT

  1. Client A is sharing some rare files with a queue of 5000 and an average uptime of 20-30 hours and an average downtime of 10-20h.
  2. When joining the queue without SLS, you always end up around 5000 unless you get a lucky shot and it takes 24h to get to 4000, at which point the source disappears.
  3. Next time the source comes back, instead of having an initial wait time of 0h, you are at 24h and will start at around 4000. By the time the source disappears again, you might manage to reach 3000. Without SUQWT, you would again go back to ~5000 the next time you find the source.
  4. Step #3 repeats until you get a send slot and have a successful upload session.
  5. After the session has ended, the wait time are reset and the cycle restarts anew for the next session.

Basically, SUQWT allows one to carry wait time from previous dead-end upload queue waiting sessions over to the next upload queue sessions until one manages to get through the upload queue, somewhat like holding a spot in a waiting line by using your gym bag or other article - if you're not there, the bag stays there and people move around it. (in an ideal civilized world anyway)

SUQWT saves each upload queue client's wait time when it exits the upload queue and restore it the next time the client comes back in the queue. You can take advantage of this feature only if the clients your are downloading from have activated SUQWT.

Personal tools