-Xms1024m

-Xmx8192m

In a 64-bit environment with heavy SIF usage, keep the max heap size equal to or greater than 4 GB. If the number of ORSs is more (irrespective of active or obsolete), allocate more heap memory.

Informatica recommends to have the value of Xmx as 8 GB. If more memory is needed, add another JVM with a new clustered node.

-XX:ReservedCodeCacheSize=256m (Oracle JVM)

-XX:codecachetotal=256m (IBM JVM)

Use the platform default. Adjust if required.

Stack Size is the memory used by Java for each thread it spans. This memory is outside the heap.

If the memory is too low, the server might fail with 'StackOverFlow' error.

If the memory is too high, the server might fail with 'Out of memory' error.

If you need to fine-tune the value, analyze the heap dump to arrive at an optimal value. For a 32-bit processor, fine-tune the value to get additional memory for the heap to avoid an "Out of memory" error.

Complete analysis needs to be done to determine the garbage collection (GC) policy, if you decide to change it. Garbage collectio policies include Parallel GC and Concurrent Sweep.

For example, while Parallel GC in heavy real time usage can give longer pauses, Concurrent Sweep does not do so. You can use a combination of the policies.

See the Java Guide to set the exact parameters.

Proper analysis is required to determine the application server sizing. Different factors including average number of concurrent users, peak number of concurrent users, current data volume, rate of data growth, future data volume, Hierarchy Manager configuration, Hierarchy Manager relationship cardinality, and number of

Data Director

applications must be considered for sizing.

For assistance on server sizing, contact the Informatica Professional Services team.

Min Connection: 0

Test Connection on Lease: Disable

Statement Caching: 10

On average, each thread takes 2.5 connections. Therefore, multiply the number of concurrent threads by 2.5.

Test Connection on Lease: Disable this property to avoid additional database cost incurred.

Min Connection: In some instances, application servers might have some connection leaks with respect to rollback transaction where a connection caught in a rollback is not released to the pool. If such instances are found, you can set Min Connection to 0.

Statement Caching (WebLogic): Initially, set 10 as the minimal number.