Red Hat Bugzilla – Bug 471934
The cpu clock is setted to max with low priority processes
Last modified: 2008-12-08 16:22:31 EST
Description of problem:
I've installed folding@home, and everyone who runs it knows that the folding processes are setted with nice 19... so with fedora releases up to 9, it resulted in low cpu clock, because obviously a process with priority 19 is intended for idle use...
but with cambridge/rawhide the CPU is setted to MAX clock when running folding (I checked, and it's running with nice 19)...
I don't know if this is a bug or a developer's choice...but I don't understand why now I must destroy my cpu with low priority processes... I run 24/24 7/7 folding@home since years.... and now with fedora 10 my cpu will reach very high temperatures...
Low cpu clock with low priority processes...
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Edit /etc/sysconfig/cpuspeed, change IGNORE_NICE to 1. Pretty sure 0 has been our default for a while now.