aMule Forum
English => Feature requests => Topic started by: gav616 on February 25, 2009, 07:27:39 PM
-
I rarely look at my mule, and really rely on the auto priority system to sort the rare from well released.
Downloading overpopular files, results in these being uploaded too much of the time, (because of high requests)
I know we could just manually set these to [Very low] priority but what if you use aMuleD and don't touch your mule for days on end? all that uploading of really populated file could go on for a long time and really harm the network (rare files don't get a chance)
one of my suggestions is to expand the scale of the priority, so there is more distances between highest and lowest
for example;
Include [Very low] and [Very high] in the auto sequence
other example;
have a linear priority , 1 to 10.
or for even more distance, include the above but with non-linear
i.e.:
1..........1
2..........2
3..........4
4..........7
5.........10
6.........13
7.........16
8.........20
9.........25
10........30
.................................
of course there might been some really obvious answer but i don't know how this 'really' could be solved (or helped)
discuss?
-
Include [Very low] and [Very high] in the auto sequence
They're excluded on purpose, so the user can always set a lower/higher priority than 'auto'. Anyway, I agree that widening the range for auto-priority (i.e. giving more possibilities instead of the current three) would result in a finer-grained upload control.
-
all that uploading of really populated file could go on for a long time and really harm the network (rare files don't get a chance)
Rare stuff is rare because nobody wants it. And popular stuff is popular because everybody wants it. So why favour rare over popular ?
While downloading popular stuff there is no reason to throttle its upload and don't repay the guys you are downloading it from (by favoring stuff they don't want instead). And after completion it's up to you to stop sharing it.
This "hurt the network" stuff is overrated. You get almost every file you want completed sooner or later with a little patience. The longer it takes, the longer you share it and the more you upload of it, so it all balances out.
-
all that uploading of really populated file could go on for a long time and really harm the network (rare files don't get a chance)
Rare stuff is rare because nobody wants it. And popular stuff is popular because everybody wants it. So why favour rare over popular ?
While downloading popular stuff there is no reason to throttle its upload and don't repay the guys you are downloading it from (by favoring stuff they don't want instead). And after completion it's up to you to stop sharing it.
This "hurt the network" stuff is overrated. You get almost every file you want completed sooner or later with a little patience. The longer it takes, the longer you share it and the more you upload of it, so it all balances out.
I sort of agree,
but my problem I've seen, is completed files on a basically unattended mule,
I've seen gigs and gigs of over requested files being upload (regardless of credit), instead of pushing (excuse my wording) rare files.
I'm basically requesting a more tighter 'auto' priority,
not actually excluding files altogether, sorry if that was implied ...
-
has someone changed the priority code? its seems 'better' in latest build (9501)
over-requested (popular files) are not being 'pushed' 'as much'...
if this is a placebo , I'm liking it :D
-
if this is a placebo
Should be.
-
I've just read this is the wiki, it explains my reasons for the auto option to be improved more clearly;
Not a really network fault but rather credit system behavior: if you share too many overpopular completed files, you may end up uploading almost only these files and very few useful uploads of files you're currently downloading. Hence, you will not get too much credits on remote clients which are useful for you and hence you may have low download speeds. aMule normally adjusts upload priority automatically so this effect should be somewhat limited but still may appear sometimes. You may want to lower upload priorities of overpopular completed files even more and boost upload priority of partially downloaded files higher. If you're suffering from this effect a way too much, you may even want to move away some overpopular files from shared folders. Please do so only if share ratio of file achieved values close to 1.0 or better to be fair. Moving away rare files makes little sense and only harms files availability. Do not do so. Technically, best possible speeds for huge files are usually achieved when you're sharing only what you're downloading, have very fast upload speed and there is lots of clients downloading same file as you do - uploading at big speeds to proper clients ensures that you will get downloads in return because of credit system. In real world your mileage may vary depending on settings, files and available upload bandwidth. Having dozen of rare files shared almost harmless (except some small overhead) since their uploads are rare and it makes network better. But sharing hundreds of completed overpopular files at once could be a bad idea sometimes. However, if you want to obtain good download speeds what really matters is a good upload bandwidth. Without good upload bandwidth you will not get too much credits regardless of any other actions. So if you can choose ISP, you may want to select ISP offering best upload speeds possible.
-
i thought of another idea,
why not also base the 'wider range' on current 'seen' completed sources
i know that each client would be different (depending on if there connect to ed2k/KAD or both) but I don't think it would matter,
-
You want to set the upload priority of a file you are downloading to "very low" automatically ? I would call that leeching.
And I don't find it helpful either to rewarm the subject on the bugtracker.
-
Well, I think it is a very discussable question!
For me, releasing I increased the Release (PS) Priority to 10000, to be sure only this file get's uploaded, which is what I need releasing ;)
For the other priority question: Auto-priority cares about full sources, right?
-
Releasers are excused from the discussion. 8)
Otherwise - if I download a file and upload it to someone, I want something back. And I don't care about "the greater good of the network" that the dude is currently uploading some "rare" file instead. I don't accept that as excuse for leeching from me.
Clients with CA will ban him probably. :P
-
Releasers are excused from the discussion. 8)
Otherwise - if I download a file and upload it to someone, I want something back. And I don't care about "the greater good of the network" that the dude is currently uploading some "rare" file instead. I don't accept that as excuse for leeching from me.
Clients with CA will ban him probably. :P
priority is just a guide for the look of your queue, clients that give you more then you give them (credit), get a boost regardless of file priority, so the "the greater good of the network" would still be "fixed" (this feature request) but your also still giving back what you owe.
obviously Release priority overrides all this (human input always does), but, still, people in credit would still get a slot first if they happened to want that file.
basically all am saying is, this feature request should not affect tit-for-tat credit at all.
-
Yes, but this feature request is about balancing uploads more smoothly. I personally would welcome it, since currently I occasionally have to set things on "Very Low" myself.