Summary of parameters affecting performance in WebLogic __web

1.
　　

Name	Parameters	Position	Role
Cache	Max-beans-in-cache	Weblogic-ejb-jar.xml	The size of the entity bean cache space, if the cached space is too small, some beans are stranded in the database and must be reloaded from the database the next time they are called
"%java_home%/bin/java"-hotspot-xms512m-xmx512m-classpath%classpath%-	startwls.cmd/startwls.sh	To achieve high-performance throughput, set the Java heap's minimum value to be equal to the maximum value.

　　
2. WebLogic parameters that affect server performance
　　
　　　

Name	Type	Position	Value
Nativeioenabled	Server	Mydomain->servers->myserver->configuration->tuning-> "Enable Native IO"	TRUE to indicate that the server uses local I/O
Socketreaders	Server->configuration->tuning	Set the percentage of the socket readers to be dedicated in the execution thread
Maximum Open Sockets	Maximum number of open sockets
Stuck Thread MaxTime	Block thread time, more than this time no return of the execution thread, the system will think is blocking the thread If WebLogic thinks all the threads in a queue are all blocked, WebLogic will increase the number of threads executing. Note: Once the number of execution threads increases, the current WebLogic does not reduce him, and if some threads are added again to the overflow warning, WebLogic will continue to increase the number of threads to execute until the upper limit is reached.
Stuck Thread Timer Interval	System checks the time interval for blocking threads
Low Memory GC Threshold	When the available memory is less than this percentage, the garbage collection starts
Low Memory granularity level	When the available memory changes for two detections exceed that percentage, the garbage collection starts
Low Memory Sample Size	Number of samples taken in a single test
Low Memory time Interval	Test interval time
Accept Backlog	The maximum number of TCP connections in the wait queue can wait for processing, indicating that the value is set too low if many client connections are rejected and no errors are displayed on the server side. If you receive a connection refused message when you connect, you should increase the value by 25% each time
ThreadCount	Executequeue	Console:mydomain->servers->myserver->monitoring->monitor all Active queues ...->configuration-> Weblogic.kernel.default->	The number of execution threads that the server initially created, setting the principle: Increasing the maximum number of concurrent threads for the machine maximizes processor utilization. For more threads on server-side operations, the thread count should be reduced, and the thread count should be increased for more client operations. The number of concurrent threads is theoretically equal to the number of +stuck threads in the local host CPU, which is sufficient to reduce system performance.
Queuelength	The number of requests in the waiting queue is 0 in the ideal state
Queuelengththresholdpercent	A percentage, when the number of the request reaches this ratio of the queue length, the WebLogic will issue a overflow flag message
Threadsincrease	If WebLogic emits overflow flag information, WebLogic attempts to increase the number of execution threads to resolve the conflict
Threadsmaximum	Maximum number of execution threads
Threads Minimum	Minimum number of execution threads
ThreadPriority	Thread Priority
Initial Capacity	Jdbc	mydomain-> JDBC Connection pools->configuration->connections	Initial Database Physical connection number
Maxcapacity	Maximum number of database physical connections
Capacity Increment	Increased number of physical connections per database
Statement Cache Type	Prepared statements caching strategy, the LRU algorithm will be the least frequently used statement to adjust the cache when a new statement arrives. The algorithm of the fixed algorithm for FIFO
Testconnectionsonreserve	Testconnectionsonreserve set to False (default setting). If this parameter is set to True (true), the connection is tested before it is assigned to the caller, which requires additional connections to the database
Statement Cache Size	Static caching of macro statements, size specified by JDBC Connection pool configuration, resizing this value to improve system efficiency
Login Delay	Time delay when creating a physical connection to a database

3. Change WebLogic to run time mode
a). Run-time mode for all domains running on a weblogic host for change, open Wl_home/common/bin/commenv.cmd (Windows) or wl_home/common/bin/commenv.sh with a text editor ( UNIX), Wl_home is the path to install WebLogic.
To change the Run-time mode for the specified domain, open domain-name/startweblogic.cmd (Windows) or domain-name/startweblogic.sh (UNIX) with a text editor. Domain-name is the directory of the domain that was created.
b). In this script, change the value of the Production_mode if you want the server to run in the product mode and specify that its value is true.
4. Select JRockit as a virtual machine
5.weblogic-ejb-jar.xml affects performance parameters
　　
　　
　　
　　
　　
　　
　　
　　
　　

Elements	Explain
Max-beans-in-free-pool	Set the EJB pool size for session and Message-driven beans
Initial-beans-in-free-pool	Adjust the pool size for the start state of the stateless Sessions beans
Max-beans-in-cache	Set buffer size for stateful session and Entity beans
Concurrency-strategy	Defining Database Locks
Isolation-level	Set TRANSACTION ISOLATION LEVEL
Relationship-caching	Entity Beans Associated buffering support