Bug 386161
Summary: | cpu stay slow when running nice >0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mélanie Legault <m1399> |
Component: | cpuspeed | Assignee: | Jarod Wilson <jarod> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
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: | 2007-11-20 20:28:39 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
Mélanie Legault
2007-11-16 02:43:21 UTC
This behavior is controlled by the the value of /sys/devices/system/cpu/cpu[0-9]*/cpufreq/ondemand/ignore_nice_load, which it would appear you have set to 1. Sounds like basically what you want to do is flip the ignore_nice_load value to 0 for all your cpus. Documentation/cpu-freq/governors.txt in the kernel source says the following: ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilisation' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation. This is useful if you are running a CPU intensive calculation on your laptop that you do not care how long it takes to complete as you can 'nice' it and prevent it from taking part in the deciding process of whether to increase your CPU frequency. This should be configurable via the IGNORE_NICE param in /etc/sysconfig/cpuspeed, so just bounce cpuspeed after changing the value and you should be all set. Of course, my own system has IGNORE_NICE=0 in its config file, and the actual system state was 1 until I restarted cpuspeed a minute ago, so something else may be amiss too... (I'm wondering if gnome twiddles that at all). But I'm pretty sure there's not a bug in either cpuspeed or the kernel. |