From: Jan Rychter <jan@rychter.com>
To: cpufreq@www.linux.org.uk
Subject: Speedstep: how often?
Date: Thu, 18 Sep 2003 23:54:45 -0700 [thread overview]
Message-ID: <m2ekydtgi2.fsf@tnuctip.rychter.com> (raw)
How often does it make sense to "speedstep" Intel CPUs?
I do realize that the question is a little vague -- please allow me to
specify some context. XEmacs is the most frequently used application on
my laptop. I've been trying various power management daemons that change
the CPU frequency. However, they all base their decisions on past CPU
usage, which is totally wrong in my case. I need a speed boost when I
press some keys or enter a short-lived CPU-intensive function. Usually
when the daemon kicks in, it is already too late.
So, I've been thinking about instrumenting XEmacs (or parts of it) so
that it can tell the power management layer that it is going to need the
CPU now, and tell it that it's mostly done with the CPU.
Question is: how often does it make sense to do that, both from a
performance and power point of view? E.g. there is probably both a delay
penalty and a power hit when you speedstep a CPU?
Can I speedstep up/down at every keystroke (which produces a change at
up to 20 times a second)? Once per second? Or even less often?
I'm currently interested in the P-IIIM, but answers for any CPU are
appreciated.
--J.
reply other threads:[~2003-09-19 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ekydtgi2.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
--cc=cpufreq@www.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox