If you are running services and P6 on the same server, you should keep the defaults. If you want the server to check for overallocations immediately, you should set the Interval low (for example, 10s) and the Concurrent Threads high (for example, 20). Remember that if the server is actively checking for overallocations, all users will experience delays in the application.
Note: Enable the Project Arbiter service because projects will be published before running the overallocation service.
To set your overallocation check settings:
- Open the Primavera P6 Administrator.
- In the Configurations drop-down list, select your configuration.
- In the sidebar select Services/Job Services.
- Select Overallocation Check.
- In the Interval field, enter the amount of time to wait before running the next available job (in 1d1h1m1s format, specifying only numbers without letters implies milliseconds).
The default value is 30s.
Enter a value between 1s and 24d20h31m23s647.
- In the Concurrent Threads field, enter the number of processes used for this service on this server. A value of 0 indicates that that this job will not run on this server.
The default value is 2.
Enter a value between 0 and 20.
- In the Active Mode field, select true if you want jobs processed continuously until all jobs finish. Select false if you want each job processed according to the Interval.
- In the Interval field, enter the amount of time to wait before running the next available job (in 1d1h1m1s format, specifying only numbers without letters implies milliseconds).