On 6/1/11 8:49 AM, Win Htin wrote: > Thanks everyone for the various answers. > The culprit was indeed "cpuspeed". I don't know how I overlooked that. > > Next question is, is it a good idea to run the "cpuspeed" service? Any > negative effects seen such as the CPU speed not ramping up properly > etc?
Win, As I understand it, leaving something like cpuspeed in place for generic workloads is fine. You'd have to watch your workload to see if you need to tweak cpuspeed to match your need for speed. :) The nice thing about ramping the speed down is power and cooling requirements are low when your server is idle. If you disable cpuspeed or set it to full performance, your CPUs will run at 100% all the time wasting power and putting out a good amount of heat for no reason. A good overview (although with a Thinkpad focus) is here: http://www.thinkwiki.org/wiki/How_to_make_use_of_Dynamic_Frequency_Scaling IBM also has an excellent guide on using CPU demand scaling for power management (RHEL 5.3-based): http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/liaai-cpufreq.htm /Brian/ -- Brian Long | | Corporate Security Programs Org . | | | . | | | . ' ' C I S C O _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
