bind_cpu_saver
                no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | bind_cpu_saver [2006/07/11 04:57] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | # $EPIC: bind_cpu_saver.txt, | ||
| + | ======Synopsis: | ||
| + | [[bind]] <key> cpu_saver | ||
| + | |||
| + | ======Description: | ||
| + | This keybinding immediately switches the client to CPU saver mode. | ||
| + | |||
| + | Normally, when CPU saver is inactive, the system clock, notify system, and mail | ||
| + | checking occur via regular intervals controlled by [[set CLOCK_INTERVAL]], | ||
| + | [[set NOTIFY_INTERVAL]], | ||
| + | activated, these sets are ignored, and the interval given by [[set | ||
| + | CPU_SAVER_EVERY]] is used instead. | ||
| + | |||
| + | When you are logged out or away from the keyboard for a long period of | ||
| + | time, it is usually not time critical that your system clock update | ||
| + | exactly at the top of the minute, or that your notifies fire exactly  | ||
| + | every minute, or that mail is detected the same minute it arrives. | ||
| + | You can save a lot of CPU usage by only doing these checks periodically | ||
| + | while you are away. | ||
| + | |||
| + | ======History: | ||
| + | This keybinding first appeared in EPIC4pre0.041. | ||
bind_cpu_saver.txt · Last modified: 2006/07/11 04:57 by 127.0.0.1
                
                