The Thread Pool performs background job work. These settings control how many thread pools are available and how long any job can use them. Oracle recommends you keep the defaults because they will provide optimal service for most environments. Change the defaults only if you are configuring a large amount of services (scheduler, leveler, apply actuals, etc.).
To set your thread pool settings:
- Open the Primavera P6 Administrator.
- In the Configurations drop-down list, select your configuration.
- In the sidebar select Thread Pool.
Note: Changes to these settings require you to restart the P6 server.
- In the Number of Threads field, enter the number of server threads.
The default value is 50.
- In the Maximum Task Duration field, enter the maximum amount of time a task can use a thread from the P6 thread pool. Only the P6 activity view uses the P6 thread pool.
The default value is 5m.
Since database transactions can run inside the P6 thread pool, Oracle recommends setting the duration to be longer than the Regular Connection Pool's Maximum Lease Duration setting.
Notes:
- A thread from the P6 thread pool can only be interrupted when it is in a wait condition (such as waiting for a database request to complete).
- See Configuring Connection Pool for Database Instance Settings for related settings.
- In the Maximum Long Running Task Duration field, enter the maximum amount of time a long running task can run before being interrupted and canceled. This setting is used for Job Services (scheduler, summarizer, and leveler), which use the P6 Long Running Thread Pool.
The default value is 20m.
Oracle recommends you set the Maximum Long Running Task Duration for the thread pool to a value longer than the Long Running Connection Pool's Maximum Lease Duration.
- In the Maintenance Frequency field, enter the frequency at which threads are checked for excess time durations.
The default value is 45s.
- In the Number of Threads field, enter the number of server threads.