aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000854aMuleFeature Requestpublic2006-03-27 17:242006-05-24 03:51
Reportereqpe 
Assigned ToKry 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Fixed in Revision
Operating SystemAny
Summary0000854: hasher priority control
Descriptionhasher could be a independent process or at least should have a prio controlling feature. it would be useful hen it has huge amounts of data to hash. now heavy hashing will stop other things mule do
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2006-03-27 17:24eqpeNew Issue
2006-03-28 14:36KryStatusnew => assigned
2006-03-28 14:36KryAssigned To => Kry
2006-03-28 14:37KryNote Added: 0001930
2006-03-29 15:48XaignarNote Added: 0001931
2006-03-29 19:42KryNote Added: 0001932
2006-05-24 03:51KryOperating System => Any
2006-05-24 03:51KryNote Added: 0001998
2006-05-24 03:51KryReproducibilityalways => N/A
2006-05-24 03:51KryStatusassigned => closed
2006-05-24 03:51KryResolutionopen => no change required

Notes
(0001930)
Kry   
2006-03-28 14:37   
It is a different thread with lower priority assigned.
(0001931)
Xaignar   
2006-03-29 15:48   
I'm not sure what can be done here. On CVS at least, all hashing is done on a thread that is run at lowest priority.
(0001932)
Kry   
2006-03-29 19:42   
Xaignar is a PARROT
(0001998)
Kry   
2006-05-24 03:51   
Closing (NAI)