There are two configuration files that let you control how the Hotspot VM behaves. Both
.hotspotrc and .hotspot_compiler are optional and not supported and can go away at any time. The easiest place to put these files is the application directory that you want controlled, that limits the scope of these files and prevents unusual things happening to other Java applications. Both files have very simple syntax, in the case of .hotspotrc which lets you set VM settings without having to specify them on the command-line. The syntax is the same as on the commandline, minus the class name and Java launcher
-Xms512m
-Xmx1024m
That would let your heap grow from a minimum of 512mb to a maximum of 1024mb inclusively. You can set any standard VM option in the
.hotspotrc file and it'll be as if the option was specified on the command line. The .hotspot_compiler file lets you exclude methods from being compiled. If you want to exclude A.B.C.D::methodName(), the syntax is:
exclude A/B/C/D methodName
Now when you run your application the Compiler will realize that A.B.C.D::methodName() should not be compiled, and will print out on the console :
### Excluding compile: A.B.C.D::methodName
