The steps needed to increase JVM:
- Log in to the Administration Console.
- Click Environment, then Servers.
- Click a Managed Server name.
- Open the Configuration tab.
- Open the Server Start tab in the second row of tabs.
- Include the memory parameters in the Arguments box, for example:
-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m
Note:
CompileThreshold: A lower setting for CompileThreshold will trigger compilations of hot methods sooner. However, the compiler has less profile information for those methods and can't always apply all the available optimizations as it needs to make more conservative assumptions. As we run in the interpreter for a longer period of time, more profile information is collected and better assumptions can be made, which results in better generated code.
MaxPermSize: Permanent generation (MaxPermSize setting) is separate heap space that is not garbage collected (ergo the permanent). Whatever is allocated to perm is in addition to the heap set with -Xmx.
Note that
PermSize is additional to the -Xmx value set by the user on the JVM options. ButMaxPermSize allows for the JVM to be able to grow the PermSize to the amount specified. Initially when the VM is loaded, the MaxPermSize will still be the default value (32mb for -client and 64mb for -server) but will not actually take up that amount until it is needed. On the other hand, if you were to set BOTH PermSize and MaxPermSize to 256mb, you would notice that the overall heap has increased by 256mb additional to the -Xmx setting.
The memory parameter requirements may differ between various JVMs (Sun, JRockit, or others).
Save the configuration changes and Restart all running Managed Servers.
Post Based on:
