Java_opts, as the name implies, is a variable used to set JVM-related run parameters. In Tomcat, it is generally set in the $catalina_home/conf/catalina.sh file, for example:
Java_opts= "-server-xms2048m-xmx2048m-xss512k-xx:permsize=128m-xx:maxpermsize=256m"
-server: Must be the first parameter, the performance is good on multiple CPUs
-xms: Initial heap size, minimum memory used, high CPU performance when this value should be larger
-xmx:java heap maximum, maximum memory used
The above two values are the minimum and maximum memory allocated for the JVM, depending on the size of the hardware physical memory, and are recommended to be half the physical memory.
-xx:permsize: Set a permanent storage area for memory
-xx:maxpermsize: Set a permanent save area for maximum memory
-xx:maxnewsize:
-XSS This causes JBoss to consume 512K of memory as soon as each additional thread is added (thread), and the best value should be 128K, and the default value appears to be 512k. The
+xx:aggressiveheap will make XMS meaningless. This parameter allows the JVM to ignore the XMX parameter, frantically eating a g of physical memory, and then eating a G swap.
-XSS: Stack size per thread
-VERBOSE:GC actual garbage collection information
-xloggc:gc.log specify garbage collection log file
-xmn:young generation heap size, Typically set to one of 3, 4 of XMX
-XX:+USEPARNEWGC: Shorten the time collected by minor
-XX:+USECONCMARKSWEEPGC: Shorten the major collection time
The following gives the Java JVM in 1G memory environment The parameter Settings reference: java_opts= "-server-xms800m-xmx800m-xx:permsize=64m-xx:maxnewsize=256m-xx:maxpermsize=128m- Djava.awt.headless=true "
Tomcat Settings java_opts