Batch Processing ADF Server Performance

8-22 Oracle Fusion Middleware Performance and Tuning Guide

8.3.5.3 AM Pool Resource Cleanup Configurations

These parameters affect the frequency and characteristics for AM pool resource cleanups. Details about resource cleanup can be found in the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. For memory-constrained systems, configure the AM pool to clean up more AM instances more frequently so that the memory consumed by the AM instance can be freed for other purposes. However, reducing the number of available AM instances and increasing the frequency of cleanups can result in higher CPU usage and longer response times. See Table 8–11 for more information. The AM pool can be configured to reduce the need for CPU processing by allowing more AM instances to exist in the pool for longer periods of time. This generally comes at the cost of consuming more memory. Table 8–10 AM Pool Sizing Configurations - CPU Considerations Parameter Description jbo.ampool.initpoolsize Set this value to the number of AM instances you want the application pool to start with. Creating AM instances during initialization takes the CPU processing costs of creating AM instances during the initialization instead of on-demand when additional AM instances are required. jbo.recyclethreshold Configure this value to maintain the AM instances affinity to a users session. Maintaining this affinity as much as possible save the CPU processing cost of needing to switch an AM instance from one user session to another. Table 8–11 AM Pool Resource Cleanup Configurations - Memory Considerations Parameter Description jbo.ampool.minavailablesiz e A setting of 0 zero shrinks the pool to contain no instances when all instances have been idle for longer than the idle time out. However, a setting of 1 is commonly used to avoid the costs of re-creating the AM pool jbo.ampool.maxavailablesiz e A lower value generally results in more AM instances being removed from the pool on a cleanup. jbo.ampool.timetolive A lower value reduces the time an AM instance can exist before it must be removed at the next resource cleanup. jbo.ampool.maxinactiveage A low value results in more AM instances being marked as a candidate for removal at the next resource cleanup. jbo.ampool.monitorsleepint erval This controls how frequent resource cleanups can be triggered. Configuring a lower interval results in inactive AM instances being removed more frequently to save memory. Table 8–12 AM Pool Resource Cleanup Configurations - CPU Considerations Parameter Description jbo.ampool.minavaila blesize and jbo.ampool.maxavaila blesize Setting these to a higher value leaves more idle instances in the pool, so that AM instances do not have to be recreated at a later time. However, the values should not be set excessively high to keep more AM instances than can be required at maximum load. Oracle Application Development Framework Performance Tuning 8-23

8.3.6 ADFc: Region Usage

Adding regions to a page can be a powerful addition to the application. However, regions can be a resource-intensive component on the page. For better performance, consider using regions only when the specific functionality is required.

8.3.7 Reusing Static Data

If the application contains static data that can be reused across the application, the cache data can be collected using a shared application module. More information on creating and using shared application modules can be found in Sharing Application Module View Instances in Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework.

8.3.8 Conditional Validations

For resource-intensive validations on entity attributes, consider using preconditions to selectively apply the validations only when needed. The cost of validation must be weighted against the cost of the precondition to determine if the precondition is beneficial to the performance. More information on specifying preconditions for validation can be found in How to Set Preconditions for Validation in Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. jbo.ampool.timetoliv e A higher value increases the time an AM instance can exist before it must be removed at the next resource cleanup. jbo.ampool.maxinacti veage A higher value results in fewer AM instances being marked as a candidate for removal at the next resource cleanup. jbo.ampool.monitorsl eepinterval Configuring a higher interval results in less frequent resource cleanups. Table 8–12 Cont. AM Pool Resource Cleanup Configurations - CPU Considerations Parameter Description