Summary

Important: These settings should be configured only by your PayGlobal Consultant or your network administrator and should not be changed without consultation.

The Set Application Priority command enables you to control the number of Central Processing Unit (CPU) cycles that PayGlobal uses in relation to other applications running at the same time.

Example

For example, a company might simultaneously run PayGlobal, Internet Explorer (IE) and some other application. Of a total of ten CPU cycles, Windows could allocate five to PayGlobal, two to IE and three to background system maintenance tasks. Alternatively the ratio could be 2:4:4.

Priority Settings

There are two main sections in this window:

• Normal Priority Settings

  For the general running of PayGlobal - linked to HR.exe.

• Busy Priority Settings

  For when the progress bar is shown, usually when someone is doing substantial processing - linked to PGReports.exe and PGPRocessing.exe.

  Wait x seconds before lowering priority: This value applies only to updating the PGProcessing.exe progress bar.

Within each of these settings, the Application Main Thread Priority and Application Priority Class combine to give an average setting.

Application Main Thread Priority

Use Application Main Thread Priority to differentiate the relative priorities of the tasks of a process. For example, a thread that handles input for a window could have a higher priority level than a thread that performs intensive calculations for the CPU.

Application Priority Class

Use Application Priority Class to differentiate between applications that are time-critical and those that have normal or below normal scheduling requirements.

General Usage

If one person within a company is running a report or closing a pay in PayGlobal while others are entering data, the Normal Priority Settings can be set to High and the Busy Priority Settings to Low. This means the report or pay close will be relatively slow but other users can carry on as normal.  If degradation of service is noticeable when entering data, the Busy Priority Settings can be lowered further.

The settings range from Idle (where tasks are done only if nothing else is running) to Highest (for example, for sound). The recommended setting for all areas is Normal.

The Busy Priority Settings allow for a certain amount of delay in processing, which is suitable for reports and pay closes but not for entering data. The manager or supervisor can determine the number of delay seconds in the edit box ''Wait _ seconds before lowering priority."

Important: When manipulating priorities, be very careful to ensure that a high priority thread does not consume all of the available CPU time. Using the Highest setting for Application Priority Class may cause disk caches to not flush and the system to hang.

ASP

In Application Service Provider (ASP) deployment, Application Priority is usually controlled by the ASP Manager at the Server.

In-house

For an in-house system, a supervisor can adjust the Application Priority in Company Settings. If '/ASP' or 'Enforce ASP' is applied, the OK button is disabled. This can be overridden with /Set Priority.