If the process "printSaver.exe" is taking high CPU usage (90%), please check the followings: If CZ Print Job Tracker is run as a windows service, the default account to run CZ Print Job Tracker service is the Local System Account that doesn't have the administrator rights on network printers (e.g. \\ print_server\ shared_printer) because it can't access the remote computer (e.g. \\print_server computer).

Answer: On NT 4.0 or higher, increasing the Idle Sensitivity will decrease the CPU usage of a 16-bit process. The Idle Sensitivity can be set under the properties of the 16-bit executable Misc tab.

Please increase the value of Monitor->Tools -> System Setting -> Supervision interval, thus reduce the frequency of supervision activities, which require CPU power. This is caused by mismatched password between Monitor and Clients. NetWatcher Monitor could set up a password for all NetWatcher Clients online, preventing from unauthorized access. The theory behind this is given as follows: Monitor could only set up a supervision password for online Clients.

When you distribute a new group policy, all the application hashes are re-computed. This usually causes a temporary CPU usage spike.

There is currently no "nice" call in hypermail to limit itself. Maybe we can consider it in the future. You might run it as a subcommand to nice. For example in an aliases file: "|nice someval 'hypermail command line'" I've NEVER tried this so... ;) You might also be looking at a very large archive with lots of messages being the cause. If so then try breaking it up into smaller archives such as monthly archives. Tools are available for that in the latest release.

You can monitor the CPU usage of your account from the Load Stats section of your control panel, which is located under Live Stats. Use the Show/Hide Help link to display the help, which explains what each of the columns in the Load Stats table shows.

Every hit/request made by your account to the CPU requires a certain time to be executed. Our system measures these hits/requests and the CPU time that they use. This includes scripts, applications, web pages, basically all activity of your account. Our system uses a complicated algorithm to calculate what part of the CPU time your account has used for the past 24 hours.

All hosting accounts on a server share the same resources, in means of CPU time, memory, disk space, bandwidth, etc. To ensure the stability of the server and a good performance, certain limits need to be set in order to avoid cases when a single account is using all resources, thus making other people's accounts to work slow. One of the limitations is in regards to the CPU usage.

RML) Yes, as of 2.5.8 the Linux kernel supports binding a process to a particular CPU. Patches exist for the 2.4 kernel series but are not yet merged (as of 28-APR-2002). This is called "task CPU affinity" and the interface was implemented via the following syscalls: which set and get a given task's CPU affinity, respectively. Utilities for manipulating affinity and the patches for 2.4 are available at kernel.org.

Check your response time settings. On the other hand, the KDE2.0 version is not yet really optimized. This will improve, and until then no real prediction can be made how fast artsd can or can't be.

MadTracker has a high-quality playback engine (check the About page), and because of that needs quite a lot of power. The minimum recommended configuration is a Pentium 166 MHz with 32 MB RAM. The optimal configuration would be a Pentium 233 MHz with 64 MB RAM under a NT-based (real 32-bit) version of Windows (NT 4, 2000 or XP). You must have a motherboard with the bugged 686b southbridge. Check The 686b bugfix for more information about this bug and the solutions to solve the problem.

Memory usage is known to climb up and drop back repeatedly when using java jre 1.4.2 with some configurations. The cpu load is higher too.

If you don't have the speed limiter on, Project64 will attempt to run a game as fast as your system possibly can and so your CPU will be fully loaded regardless of how fast your system is or which game it is etc. If you do have the limiter on, this is a sign that your system is not fast enough to run the emulator at full speed in the given situation and configuration.

This process is a single thread running on each processor, which has the sole task of accounting for processor time when the system isn't processing other threads. In Task Manager, expect this process to account for the majority of processor time. The system idle process uses all the CPU time that is not used by anything else. CPU time is like any other time; you can't not use it. If you do nothing, you're still using time: you are using time to do nothing.

When idle or during a session, the CyberGatekeeper agent takes up less than 2% of CPU time. When a new session is initiated, it uses more CPU, for a short period (about 1 second). It then drops to the nominal idle usage.

There may be several reasons that your usage could be unusually high. The first thing to check is a leaking toilet or other plumbing fixtures. The other reasons could be due to excessive lawn water, during summer or it is possible the meter was misread. If you have any questions regarding usage please contact the Water Department's Billing Personnel and we will gladly check your reading.

The problem is an implementation issue with the Sun's Java for Linux. The Sun Java VM process appears to be using a lot of CPU because of the way it is polling the sockets for data, but the Java process should be yielding to other processes on the system. The CPU load seems to be the same whether it's 1 stream or 100.

Many bass notes in combination with the sustain pedal means that there will occur lots of computations for the CPU. Most modern CPUs can handle this fine.

This is a known problem with the i810 audio chipset and RAT. You will have to enable Stereo mode for RAT. To do that see this website for instructions, http://www.ap-accessgrid.org/AG2/intel8x0.html.

This is a critical point for us since the less loaded our servers are the less management we have to do and the better the customer experience. Our main goal is to keep CPU utilization as low as possible even during peek periods.