Hosted by:

wrapper.ntservice.process_priority Property

wrapper.ntservice.process_priority Property

Configuration Property Overview

- Configuration Property Overview
- Windows NT/2000/XP Configuration Properties
- Property List by Name

wrapper.ntservice.process_priority

Specifies the priority at which the Wrapper and its JVM will be run at when run as an NT service or as a console application. Possible values are `LOW`, `BELOW_NORMAL`, `NORMAL`, `ABOVE_NORMAL`, `HIGH`, and `REALTIME`. Defaults to `NORMAL`. `BELOW_NORMAL` and `ABOVE_NORMAL` are not supported on Windows NT, 95 or 98.

Example:

    wrapper.ntservice.process_priority=NORMAL

WARNING

Changing this property to HIGH or REALTIME makes the Wrapper and its JVM consume all available CPU first. It will only yield CPU to other processes when it does not need the cycles itself. This will cause a number of problems including an unresponsive UI.

We have seen problems with time-outs, between the Wrapper and its JVM, when the JVM is outputting large quantities of console output and consuming 100%, for long periods of time. If you change this default value and are experiencing such time-outs, please return the property to the default NORMAL priority before contacting support.

NOTE MEG |  | Reloading the Wrapper configuration will have no effect on the priority of the Wrapper process. But the priority of the restarted JVM process will take on the updated value.

NOTE MEG

From the Windows API, each priority level is described as follows:

NORMAL
| Specify this class for a process with no special scheduling needs.
LOW
| Specify this class for a process whose threads run only when the system is idle. The threads of the process are preempted by the threads of any process running in a higher priority class. An example is a screen saver. The idle-priority class is inherited by child processes.
HIGH

Specify this class for a process that performs time-critical tasks that must be executed immediately. The threads of the process preempt the threads of normal or idle priority class processes. An example is the Task List, which must respond quickly when called by the user, regardless of the load on the operating system. Use extreme care when using the high-priority class, because a high-priority class application can use nearly all available CPU time.

REALTIME
| Specify this class for a process that has the highest possible priority. The threads of the process preempt the threads of all other processes, including operating system processes performing important tasks. For example, a real-time process that executes for more than a very brief interval can cause disk caches not to flush or cause the mouse to be unresponsive.

by Leif Mortenson

Copyright ©1999-2004 by Tanuki Software. All Rights Reserved. | last modified: