Configuring Project Hierarchy Cache in Services Settings

If you are running services and P6 on the same server, you should keep the defaults. If you want to apply the cache immediately, you should set the Frequency low. Remember that if the server is actively applying the cache, all users will experience delays in the application.

To set your project hierarchy cache settings:

Open the Primavera P6 Administrator.
In the Configurations drop-down list, select your configuration.
In the sidebar expandServices, then expand Publication and select Infrastructure Services.
In the Project Hierarchy Cache area:
1. Choose whether to select Enable WBS Hierarchy Preload.
  This setting is applicable to all users not assigned the Admin Superuser global security profile. It is relevant when users open any page that requires project data, such as the EPS page, View Service Status, or the OBS structure.
  
  If this setting is selected, when a user opens a page that requires project data, P6 loads into cache the WBS hierarchy for all projects that user can access. After the WBS data is cached, P6 can retrieve it more quickly than if it must query the database. This setting can improve responsiveness in smaller environments with fewer users and simpler project structures. However, in larger environments with many users having access to many complex projects, pre-loading the WBS hierarchy to server cache can degrade performance. Therefore, Oracle recommends clearing this option in large, high-volume environments.
2. In the Cache Policy drop-down menu, select the cache policy to use. The cache policy determines how much data is in the cache and which data to remove to reclaim memory.
  You can select one of the following:
  - FIFO First In First Out-projects are cleared from the cache in the same order they were added to memory.
  - LRU Least Recently Used projects are cleared from the cache before more recently used ones.
  - JVMM Java Virtual Machine Managed uses soft references to cache elements; memory used by soft references is reclaimed by the JVM as required.
  - PRR Projects are selected at random to be cleared from cache.
  - PRFIFO Periodic Refresh First In First Out is the same as FIFO, except policy is enforced based on MaintenanceFrequency.
  - PRLRU Periodic Refresh Least Recently Used is the same as LRU, except policy is enforced based on MaintenanceFrequency.
  - PRCC Periodic Refresh Clear Cache ignores CacheLimit to flush the entire cache, based on MaintenanceFrequency.
    Note The default value is PRR.
3. In the Cache Limit field, enter the maximum number of projects stored in memory.
  The default value is 5000.
  
  Enter a value between 1000 and 30000.
4. In the Maintenance Frequency field, enter the frequency for applying the specified cache policy. If you apply the cache policy, the system can reclaim memory from the cache.
  The default value is 5h.
  
  Enter a value between 1m and 24d.

Related Topics