Switching to the fastest user
Moderator: Moderators
Switching to the fastest user
Alot of times DC switches over to a source with a very low speed (<2KB/s) when i'm not looking while there are dozens of high speed sources available. This way, DC could waste a whole night/day of downloading from a lowspeed user while the file could be finished if it picked a high speed user.
I know there has been spoken a lot about this issue, a popular suggestion was to automatically drop slow users. In my opinion there is a much simpeler solution. If DC has downloaded a filelist, it can calculate the avarage speed of that user. That avarage speed should be saved along with the username, when DC has to switch over to another source, it should automatically pick the one with the highest avarage speed. The avarage speed could be updated when DC actually is downloading a file from the user.
I hope this suggestion wasn't posted before, but I think it's worth consideration.
I know there has been spoken a lot about this issue, a popular suggestion was to automatically drop slow users. In my opinion there is a much simpeler solution. If DC has downloaded a filelist, it can calculate the avarage speed of that user. That avarage speed should be saved along with the username, when DC has to switch over to another source, it should automatically pick the one with the highest avarage speed. The avarage speed could be updated when DC actually is downloading a file from the user.
I hope this suggestion wasn't posted before, but I think it's worth consideration.
A mod by xhost was made that has this type of feature (and it was rejected from being patched into DC++). In the DC++ client table, look for the clients with 'download limiting' for the clients which have this feature.
Ok, so I didn't name the featuret properly. Here is the original post by xhost+ for what you're talking about and a screenshot. The mods listed in the client table, have changed the workings around a little, but the idea remains the same.
Why not download one of the clients, try it out, and then see if thats what you're getting after.
Why not download one of the clients, try it out, and then see if thats what you're getting after.
That suggestion is completely different. What he suggested is to drop users when the speed is below a settable value, what I suggested is to remember the speed of the users after downloading the filelist, and then to start downloading from the fastest user.BSOD2600 wrote:Ok, so I didn't name the featuret properly. Here is the original post by xhost+ for what you're talking about and a screenshot. The mods listed in the client table, have changed the workings around a little, but the idea remains the same..
-
- Forum Moderator
- Posts: 366
- Joined: 2004-03-06 02:46
-
- Posts: 184
- Joined: 2003-05-26 11:29
- Location: UK
Have you forgotten this one, you commented in the discussion.Wisp wrote:can you give an example of a similar request?PseudonympH wrote:I could swear it's in there already. Or maybe that's just the 500 people that have posted it in the forum...
http://dcplusplus.sourceforge.net/forum ... g+filelist
and another:
http://dcplusplus.sourceforge.net/forum ... g+filelist
Always remember you're unique, just like everyone else.
Both suggestions are different, they both want to improve downloading speed by using faster users, but they want to use a different method.Gasman1015 wrote:Have you forgotten this one, you commented in the discussion.
http://dcplusplus.sourceforge.net/forum ... g+filelist
and another:
http://dcplusplus.sourceforge.net/forum ... g+filelist
I think my suggestion is the simplest one.
To summarize my request:
- After downloading the filelist of a user, DC++ remembers the avarage speed of that transfer and saves it along with the username.
- DC++ makes a list of the alternate users, ordered by downloading speed (fastest first).
- When DC++ has to switch to another user, DC++ picks the first (fastest) user on the list, if there are no slots available, DC++ picks the second user from the list, and so on.
In addition to the previous post, I would like to show how I imagined this feature.
If you select a file in the download queue, you get the following 'source manager' (or whatever you would call it)
When a user is added as an alternative, the user is visible in this list which is ordered default by speed, but the user can change that. This way you can easilty select multiple users to delete. In the right-click menu you can have options like "add user to favorites", "connect to the hub", "copy nick/ip to clipboard", etc.
Maybe it's a good idea to also have an exclusion list in the same window where you can move users to (if you really don't want to download from them).
If you select a file in the download queue, you get the following 'source manager' (or whatever you would call it)
When a user is added as an alternative, the user is visible in this list which is ordered default by speed, but the user can change that. This way you can easilty select multiple users to delete. In the right-click menu you can have options like "add user to favorites", "connect to the hub", "copy nick/ip to clipboard", etc.
Maybe it's a good idea to also have an exclusion list in the same window where you can move users to (if you really don't want to download from them).
-
- Posts: 184
- Joined: 2003-05-26 11:29
- Location: UK
The principle is the same, also take note of GargoyleMT's comments.Wisp wrote:Both suggestions are different, they both want to improve downloading speed by using faster users, but they want to use a different method.Gasman1015 wrote:Have you forgotten this one, you commented in the discussion.
http://dcplusplus.sourceforge.net/forum ... g+filelist
and another:
http://dcplusplus.sourceforge.net/forum ... g+filelist
I think my suggestion is the simplest one.
To summarize my request:I haven't seen this before in other posts, they're mostly about dropping slow users, in my suggestion, you keep the slow users but lower their priority so that they are only used when there are no faster users available.
- After downloading the filelist of a user, DC++ remembers the avarage speed of that transfer and saves it along with the username.
- DC++ makes a list of the alternate users, ordered by downloading speed (fastest first).
- When DC++ has to switch to another user, DC++ picks the first (fastest) user on the list, if there are no slots available, DC++ picks the second user from the list, and so on.
Scanning other sources for speed would involve downloading portions of the file. If you're doing that, you should save those portions not to be wasteful. At that point, you've already designed multi-source downloading.
I'm not going to look into this at all, and hope that it's determined that multisource downloading will go in DC++.
These source micro-management features will all go away when you can download from more than one person.
Always remember you're unique, just like everyone else.
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us