aMule Bug Tracker - aMule
View Issue Details
0001528aMuleFeature Requestpublic2009-06-03 17:392010-03-03 02:56
0001528: Wider range of auto upload priorities
To avoid the issue raised here: [^] (5th bullet point)

and posted here: [^]
No tags attached.
Issue History
2009-06-03 17:39gav616New Issue
2009-06-03 17:39gav616Operating System => Any
2009-06-03 17:48gav616Note Added: 0003162
2009-06-03 17:49gav616Note Edited: 0003162
2009-06-03 18:05gav616Note Edited: 0003162
2009-06-03 18:21MarcellNote Added: 0003163
2009-06-03 20:06gav616Note Added: 0003164
2009-06-03 20:14gav616Note Added: 0003165
2009-06-03 20:16gav616Note Edited: 0003165
2010-03-03 02:56gav616Note Added: 0003386

2009-06-03 17:48   
(edited on: 2009-06-03 18:05)
i find manually setting massively requested files to 'very low' normally perverts the explosion of uploading for that one file.

So that might be one way to head down.

edited on: 06-03-09 17:49

edited on: 06-03-09 18:05
2009-06-03 18:21   
I agree with gav616. Setting the priority to "Very low" helps.

Nevertheless it would be useful to have aMule automatically set the priority to "Very low" for over popular files. I am not yet familiar how the popularity is determined, so I will have to take a closer look on this first.
2009-06-03 20:06   
I believe popularity is determined only by requests, regardless of how well spread each chunk is or number of completed sources..
2009-06-03 20:14   
(edited on: 2009-06-03 20:16)
i think the main question is,
is it enough to widen the auto upload range by 2: [VL, L, N, H, VH]
or is a totally different approached to upload priority needed to be looked at?

atm, I think adding a slightly wider range to the current 'emule' design would be sufficient though, just to suppress highly requested files.

edited on: 06-03-09 20:16
2010-03-03 02:56 [^]

updated url