aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: lowspeed clients manual drop  (Read 3218 times)

Morse

  • Full Member
  • ***
  • Karma: 6
  • Offline Offline
  • Posts: 105
lowspeed clients manual drop
« on: February 25, 2009, 06:46:02 PM »
Situation:

i want to download some mp3 or pdf or another file that is <10mb. let's assume that the file is popular, and amule quiqly founds 300 sources, and some of them are ready to transfer data. each of peers "allocates" some part of the file and starts the transfer of data. let's assume we have 2 peers: one with good speed and one with "almost zero". first peer transferred it's chunk, and is ready to transfer more, but there is no more "unallocated" data, so the connection is closed. the second peer would transfer its part for hours, and even if there is plenty of other peers that ready to transfer it in no time, i have to wait for this particular peer.
the file that could be transferred in a couple of minutes (or even seconds) would be ready only half a day later.

the feature requested: to make it possible to forcibly close connections with the peers whose speed is lower than a manually set treshold
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: lowspeed clients manual drop
« Reply #1 on: February 25, 2009, 09:05:12 PM »
IIRC Kry implemented a feature "drop slow source if a faster one is available" a while (some years) ago. However, I don't know if that piece of code is still working or not.
Logged
concordia cum veritate

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: lowspeed clients manual drop
« Reply #2 on: February 25, 2009, 11:56:43 PM »
Quote from: Morse on February 25, 2009, 06:46:02 PM
the feature requested: to make it possible to forcibly close connections with the peers whose speed is lower than a manually set treshold
Manually or automatically ?
If you are sitting and watching you can just stop & restart the download (and probably get a better source this time). And if not - why would you care how long it takes ?  ;)
I haven't done the math, but I don't think a source can be so slow to take half a day for a download part without the connection breaking down. Have you actually watched this ?
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

Morse

  • Full Member
  • ***
  • Karma: 6
  • Offline Offline
  • Posts: 105
Re: lowspeed clients manual drop
« Reply #3 on: February 26, 2009, 12:20:05 AM »
yes, i've actually watched it (many times i must say. not half a day of course, but half an hour for a 2mb file is just enough for me to wish this client die quick but painfully), and yes, i stopped/relaunched file because that was the only option. and i think it isn't a good one for at least one reason: i want to drop loosy peers BEFORE speedy ones finish their chunks, so that they continue to transfer data with good speed.

and honestly, i don't care whether it would be manually or automatically, i just thought manual solution would be easier to implement.
Logged

gav616

  • Guest
Re: lowspeed clients manual drop
« Reply #4 on: March 31, 2009, 04:40:32 PM »
i support something like this, because I've seen people get stuck in a slot.
a client has got into one of my  upload slots and has not received any data for over 30 mines but is not being dropped, thus causing my slot count to go crazy.

bearing in mind this is aMuleGUI, so some data could be wrong.

settings;
upload: 30
slot allo: 5

build;
aMuleD / aMuleGUI SVN r9536


« Last Edit: March 31, 2009, 04:45:51 PM by gav616 »
Logged