Managing memory usage

You may notice reduced performance when loading large files. In that case, you may want to modify the memory usage of the Provisioning Service.

Two configuration settings control memory usage in the Provisioning Service:

The maximum number of Message-Driven Beans (MDBs) allowed in the pool.
The maximum number of Message-Driven Beans for the Provisioning Service is controlled by the message-driven-bean-limit parameter in plan.xml. The default value of this variable is 2.
The Java heap space. Java heap space is controlled by the USER_MEM_ARGS= parameter in the file $DOMAIN_HOME/bin/setDomainEnv.sh in Linux, or $DOMAIN_HOME/bin/setDomainEnv.cmd in Windows.
In the line
```
USER_MEM_ARGS="-Xms256m -Xmx6144m -XX:PermSize=64M -XX:MaxPermSize=512M"
```
change -Xmx6144m to the amount of heap space you want to use. The default heap space is 6GB.

These two configuration settings are related. If you specify a larger pool of MDBs, you should also specify more heap space for the Provisioning Service. Conversely, if you reduce the amount of heap space, you should reduce the number of MDBs in the pool.

The starting estimate is 1 GB of heap space per unit in the pool. Thus, the default pool size of 6 calls for 6GB of heap space. As you use the Provisioning Service, you can fine tune these estimates to match your own needs and experience.