WebLogic Memory Tuning Instructions

One: WebLogic configuration issues:
Due to the WebLogic configuration problem, our test failed. The reason is that there is too little memory allocated for WebLogic. Increase memory allocation by modifying the Commom\bin\commenv.cmd file.
The modified sections are as follows:
: Bea
If "%production_mode%" = = "true" goto Bea_prod_mode
Set Java_vm=-jrockit
Set mem_args=-xms768m-xmx1024m
Set java_options=%java_options%-xverify:none
Goto continue
: Bea_prod_mode
Set Java_vm=-jrockit
Set mem_args=-xms768m-xmx1024m//originally was 128m~256m, too small, the data is too big
Goto continue

After the result is modified, there is no effect. There is still a case of failure.
Found, originally, in: Bea There is also a section of configuration information below:

: Sun
If "%production_mode%" = = "true" goto Sun_prod_mode
Set Java_vm=-client
Set mem_args=-xms768m-xmx1024m-xx:maxpermsize=256m
Set java_options=%java_options%-xverify:none
Goto continue
: Sun_prod_mode
Set Java_vm=-server
Set mem_args=-xms768m-xmx1024m-xx:maxpermsize=256m
Goto continue

Change the memory allocation here to take effect.
The reason for this is that the first piece of code above is set for Bea's own JVM, and the following is set for sun. and WebLogic defaults to sun, so there's something wrong with it.

After testing, the 2nd has no effect!!!!

Second, the optimization of WebLogic:
WebLogic server mainly from the memory aspects of consideration, WebLogic start a JVM virtual machine first, the JVM virtual machine occupies a memory size is also weblogic occupied memory size, in the absence of other applications, You can allocate up to 80% of the system memory for the JVM virtual machine (as large as 2G), and the other is garbage collection, where all active and dead processes exist in the JVM, and if they consume more memory than the JVM, This time the system will temporarily stop all Java applications and start a garbage collection action, of course, the shorter the better.
As a result, garbage collection is typically set up to consume 1/4 of the size of the JVM's memory, so that a garbage collection can end up in 10-20 seconds at a time. (The larger the JVM is, the longer each garbage collection (garbagecollection) interval is, but the longer each time it lasts). The JVM memory size is set within startweblogic.cmd/startweblogic.sh. In which a section will be found:

%java_home%\bin\java%java_vm%%mem_args%%java_options%-dweblogic. Name=%server_name%-dweblogic. Productionmodeenabled=%production_mode%-djava.security.policy= "%wl_home%\server\lib\weblogic.policy" WebLogic. Server
This is the system-enabled command of the JVM, where%mem_args% is the parameter variable that sets the memory, preceded by this line: Setmem_args=-xms150m-xmx256m,xms and Xmx Specify the value is the JVM occupies the memory the definition, In general, however, the two should be set to equal. Set the memory parameters of the garbage collection GC as follows (but there are still some problems with validation, further research is required) Official documentation:-XX:NEWSIZE=128M-XX:MAXNEWSIZE=128M-XX:SURVIVORRATIO=8.

WebLogic Memory Tuning Instructions