Re: Is there any valid reason to add an idiotic script to /etc/init.d by an default Debian install that only cause a PITA?
On Tue, 14 Jun 2011 18:29:36 +0200, Ralf Mardorf wrote:
> On Tue, 2011-06-14 at 16:10 +0000, Camaleón wrote: [snip]
>
> Ok, perhaps you don't have the tools to measure the load, so I won't ask
> you to do it, but ...
>
> Have you ever compared temperature and battery life when switching
> between ondemand and performance?
What temp? CPU? Hard disks? Motherboard? VGA card? When you force your
CPU to increase its cycles you are also adding extra heat to the rest of
the components. If your system is not properly cooled, all of them will
suffer.
> How much is the difference on your machine?
I have not tested but this is just a matter of physics, I guess :-)
But in this regard I put my trust in developers that have decide this
setting is the default, and should I had the reasons to do not agree, I
would just change the value to fit my needs (the same way I prefer
Postfix instead Exim or the same way I prefer "X" instead "Y"...).
> For the machines I know there's quasi no difference for he temperature
> and the measured watt, those machines don't use batteries, but watt
> gives information about battery duration.
So I guess you do have performed some tests about this so maybe you can
share your findings with us.
> On Tue, 2011-06-14 at 16:15 +0000, Camaleón wrote:
>> On Tue, 14 Jun 2011 18:02:40 +0200, Ralf Mardorf wrote:
>>
>> > Why not using ondemand set by the kernel's default governor?
>>
>> Because then you will force users to recompile the kernel
>
> Why recompiling the kernel? Why not setting the default governor to
> ondemand. I bet it's already set to ondemand.
Because someone may want to change it?
> For me it is
>
> spinymouse@debian:/boot$ cat config-2.6.39.1 | grep CONFIG_CPU_FREQ_DEFAULT_GOV_
> # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
> # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
>
> I bet for you it is already set to ondemand.
Let's see...
sm01@stt008:~$ grep -i "CONFIG_CPU_FREQ_DEFAULT_GOV" /boot/config-2.6.26-2-amd64
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
Ha! :-P
> If so, why adding the script?
To be able to change it by the user by editing one file ;-)
Greetings,
--
Camaleón
Reply to: