Re: The ondemand CPUFreq code -- I hope the functionality stays

Thomas Tuttle
2006-07-28T02:43:36Z

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

On July 27 at 21:04 EDT, Patrick McFarland hastily scribbled:
> On Thursday 27 July 2006 04:54, Miles Lane wrote:
> > Hello,
> >
> > It sounds, from comments in the discussion of CPU Hotplug locking
> > problems, as though you are considering deleting the ondemand CPUFreq
> > code. If this happens, I hope that something that provides the same
> > functionality replaces it. I really appreciate having my power
> > consumption automatically modulated on an as needed basis. Power
> > management seems to be one of the areas where there is a lot of room
> > for improvement.
>
> I think you've gotten confused. Ondemand is a horrible governor that only
> flips between two cpu frequencies, the lowest and the highest. Use the
> Conservative governor instead.

AFAIK, ondemand implements the following.

Many times per second, do the following:
Calculate CPU usage since last check.
If CPU usage > high threshold, set frequency to maximum.
If CPU usage < low threshold, lower frequency by one level.

So it will immediately jump to the highest frequency, in order to
provide low latency, but will slowly decrease it until it finds the
lowest frequency that provides enough CPU power to support the current
load.

Personally, I prefer conservative, because it isn't as "jumpy", but I
can see ondemand being necessary in a server environment where the
several second lag time to peak performance would hurt response time
when load is low.

--Thomas Tuttle

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]