20 Tuning Oracle Enterprise Scheduler Service

You can tune Oracle Enterprise Scheduler Service (ESS) to optimize its performance in enabling scheduling and running jobs.

20.1 About Enterprise Scheduler Service

Oracle Enterprise Scheduler enables scheduling and running jobs within a particular time frame, or workshift, by using rules to create work assignments.

Oracle Enterprise Manager Fusion Applications Control allows you to define, control and manage Oracle Enterprise Scheduler job metadata, including job definitions, job requests, job sets (a collection of job requests), incompatibilities (job definitions and job sets that cannot run at the same time for a given application) and schedules governing the execution of job requests.

For more information, see Introduction to Administering Oracle Enterprise Scheduler in Oracle Fusion Middleware Administering Oracle Enterprise Scheduler.

20.2 Tuning Enterprise Scheduler Service Parameters

You can tune the enterprise scheduler service parameters for optimal performance.

Table 20-1 describes the enterprise scheduler service tuning parameters.

Maximum Poll Interval is a dispatcher parameter that applies to the Oracle Enterprise Scheduler request dispatcher. The request dispatcher manages requests that are awaiting their scheduled execution. The request processor handles the job requests once they have dispatched.

Thread Count is a processor tuning parameter that applies to the Oracle Enterprise Scheduler request processor. The request processor manages job requests whose scheduled execution time has arrived, and are ready to execute.

Table 20-1 Essential Enterprise Scheduler Service Tuning

Name Symptoms Recommendations Trade-offs

Maximum Poll Interval

Default: 15 seconds

A high number of requests whose execution time has been reached and remain in WAIT state for an extended time.

If there is an excess of waiting requests that are eligible to be dispatched and processor threads are available, decrease this value .

Lowering the value increases CPU usage and database activity.

Increasing the value may delay the dispatching of requests that are ready for processing.

Thread Count

Default: 25

A high number of requests in READY state that are otherwise available for processing.

If there is a build up of requests that are ready to be executed and the increase system resource usage is acceptable, increase this value.

Lower the value to reduce the amount of system resources used for request processing.

Increasing this value increases CPU usage, memory usage, and database activity.

Lowering this value may result in a build up and potentially delay processing of requests.