When you provision an Oracle SOA Cloud Service instance and specify a compute shape, the JVM heap size for WebLogic Server and Load Balancer processes is determined automatically.
Default Heap Sizes
The compute shape you select for a WebLogic Server cluster determines the availability of RAM on VMs in this cluster, and the amount of available RAM is used to determine the preset heap size for the JVM processes running on the VMs.
The following table shows the Oracle SOA Cloud Service JVM heap size settings for each compute shape.
| Compute Shape | Min Heap Size | Max Heap Size | Configured Garbage Collector |
|---|---|---|---|
|
OC1M |
256 MB |
10 GB |
Garbage First (-XX:+UseG1GC) |
|
OC2M |
256 MB |
24 GB |
Garbage First (-XX:+UseG1GC) |
|
OC3M |
256 MB |
24 GB |
Garbage First (-XX:+UseG1GC) |
|
OC4M |
256 MB |
24 GB |
Garbage First (-XX:+UseG1GC) |
Custom Heap Sizes
Increasing the heap size for a managed server in Administration Console Online Help (12.2.1.2)
Increasing the heap size for a managed server in Administration Console Online Help (12.1.3)
Set Java options for servers started by Node Manager in Administration Console Online Help (10.3.6) (specify the Java option to increase the heap size; for example: -Xmx3g)
The heap size is also set when you choose a shape for the load balancer. You cannot change the heap size for the load balancer.