Bug 503087
Summary: | /proc/cpuinfo shows wrong values for MHz | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Brian Wheeler <bdwheele> |
Component: | kernel | Assignee: | Prarit Bhargava <prarit> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | dzickus |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-29 15:08:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Wheeler
2009-05-28 19:15:14 UTC
>model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
>stepping : 6
>cpu MHz : 1992.000
Brian,
Can you do a 'service cpuspeed status' and let me know what it says?
P.
It says: Frequency scaling enabled using ondemand governor Ah, when I turn it off then cpuinfo has the right speed reported. I tried loading the machine but it didn't seem to make a difference (I might not have loaded it for enough time, though) The machines which were reporting the right values had cpuspeed turned off. Is there an advantage to having cpuspeed turned on when running a server system? (In reply to comment #2) > It says: > > Frequency scaling enabled using ondemand governor > > > Ah, when I turn it off then cpuinfo has the right speed reported. I tried > loading the machine but it didn't seem to make a difference (I might not have > loaded it for enough time, though) > > The machines which were reporting the right values had cpuspeed turned off. Is > there an advantage to having cpuspeed turned on when running a server system? Brian, A few things: 1. /proc/cpuinfo "model name" field shows just that -- the actual model name as the processor itself indicates. So, in your case, "Intel(R) Xeon(R) CPU E5430 @ 2.66GHz" is what the CPU is telling the OS the CPU thinks it is. 2. /proc/cpuinfo "cpu Mhz" is the current CPU frequency, or the "real" frequency that the CPU is running at. This number fluctuates depending on the load that is applied to the system. 3. You can find out additional information on cpuspeed by executing a 'man cpuspeed' at a command prompt. 4. There is an advantage to having cpuspeed "on" on a server -- the system conserves power during low loads, as opposed to leaving the CPUs at their highest frequency. Or, as a fellow engineer said, "Check your power bill at the end of the month" ;) P. |