Skip to contentSkip to conversation

PROBLEM: Celeron Core

DISCUSSION Tomasz Chmielewski 3 participants 3 messages Jan 20, 2008 – Jan 21, 2008

lore
Share & tools
lore
#0 lore raw
Quoted 1 line
Quoted 1 line

Clock throttling is not likely to save your battery, unless you have tasks that are running at 100% CPU for an unlimited time or something, and you force your CPU to throttle. Normally most people have tasks that run and then the CPU idles - loading an email, displaying a web page, etc. Clock throttling will just make these tasks utilize the CPU for a longer time proportional to the amount clock throttling and therefore negate any gains in battery usage.

Aren't you forgetting about CPUfreq governors? Which mean: use the maximum CPU frequency when the system is busy, throttle down (or lower voltage) when the system is idle.

So yes, throttling will save the battery.

Besides, not all CPUs support power management (voltage control).

Quoted 2 lines

IMO clock throttling (as opposed to the reduction of the frequency of an idle CPU) is only useful for preventing the CPU from overheating.

And for reducing power on CPUs that can't do any power management, just throttling.

For example, a server that doesn't crunch any numbers at night will certainly use less power when throttled.

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#1 lore raw
Quoted 8 lines · Tomasz Chmielewski
Quoted 7 lines
Quoted 7 lines

Clock throttling is not likely to save your battery, unless you have tasks that are running at 100% CPU for an unlimited time or something, and you force your CPU to throttle. Normally most people have tasks that run and then the CPU idles - loading an email, displaying a web page, etc. Clock throttling will just make these tasks utilize the CPU for a longer time proportional to the amount clock throttling and therefore negate any gains in battery usage.

Quoted 5 lines

Aren't you forgetting about CPUfreq governors? Which mean: use the maximum CPU frequency when the system is busy, throttle down (or lower voltage) when the system is idle.

So yes, throttling will save the battery.

In the relevant documentation "throttling" usually means "the reduction of the frequency of a CPU that is not idle" in which case it won't (at least on the average).

Quoted 11 lines

Besides, not all CPUs support power management (voltage control).

Quoted 2 lines

IMO clock throttling (as opposed to the reduction of the frequency of an idle CPU) is only useful for preventing the CPU from overheating.

And for reducing power on CPUs that can't do any power management, just throttling.

For example, a server that doesn't crunch any numbers at night will certainly use less power when throttled.

You can't use less power, you only can use less energy. :-)

Anyway, that's "the reduction of the frequency of an idle CPU" mentioned above and it makes sense in the majority of cases.

Greetings,
Rafael

#2 lore raw
In reply to Tomasz Chmielewski
Quoted 7 lines · Tomasz Chmielewski

Aren't you forgetting about CPUfreq governors? Which mean: use the maximum CPU frequency when the system is busy, throttle down (or lower voltage) when the system is idle.

So yes, throttling will save the battery.

Besides, not all CPUs support power management (voltage control).

Voltage scaling isn't the only component of CPU power management. Intels have supported low power states on idle since the Pentium 90 (Cyrix had "Suspend on HALT" earlier than that), which means that an idle processor takes less power than one executing code. On anything even vaguely modern, throttling will not save you any significant power compared to the C state support.

Quoted 2 lines

For example, a server that doesn't crunch any numbers at night will certainly use less power when throttled.

Have you got benchmark figures for this?

Signature · 1 line
Matthew Garrett | [email protected]