Merciadri Luca:
> Jochen Schulz <ml@well-adjusted.de> writes:
>
>> What does
>>
>> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>>
>> say after bootup?
>>
> Ondemand, the same as what appears in the applet, after boot. However,
> despite "Ondemand", even a huge CPU load does not make Debian asking
> for more CPU resources, such as 100%.
Then have a look at
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It should contain the highest frequency your processor supports. If not,
then something strange is happening.
>> That would be the kernel's default behaviour if your
>> current governor is either ondemand or conservative.
>>
> How could I modify it?
Modify what? -Most probably, cpufrequtils will contain alle the tools
you need. It allows you to select a governor and set min/max frequency
limits, for cases where they are mis-reported by default.
>> I suggest you use just the ondemand governor and stop caring about the
>> issue at all. You will get full CPU power when you need it and save a
>> little power when you don't.
>
> My aim is not to save power. I am running many scientific-purpose
> applications, and they need full CPU power.
Sure, no problem. The ondemand governor is all about saving power
without sacrificing performance. If nothing's wrong with your
configuration, this is exactly what you should get by default.
A question that comes to my mind: how do you measure the current clock
frequency? Only by looking at the Gnome applet? I would take a look into
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq, just to be sure.
J.
--
I want to look younger than my friends so I will fight ageing as long as
I can.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
Attachment:
signature.asc
Description: Digital signature