WebLogic Core tuning:
Performance packs, blocking threads, garbage collection, block tuning, TCP buffer backlog, SSL
1. Local IO Performance Package
Start the local IO in the admin console, enabled by default, enable native IO
2. Socket Readers
The percentage of execution threads in the default queue that can be used as the socket reader, by default 30%, maximum 99%, to increase the speed and processing power of the server to accept client requests.
-dweblogic:threadpoolpercentsocketreaders=value
3. WLSX Thread Blocking
Stuck Thread Max Time
Sturck Thread Timer Interval
Struck Thread Count
Failure Action
Auto Kill if fail
4. Collection Threshold (GC)
Low memory GC Threshold (to determine lower GC threshold value)
Low memory granularity levels (determines the level of granular granularity with lower RAM)
Low memory sample size (to determine the sample sizes that are lower in RAM)
Low memory time Interval (to determine the interval at which memories are lower)
5, block adjustment
Block is a temporary buffer for IO
WebLogic JVM divides network data into blocks
Default size is 4k
You should adjust the block size for applications that use the network frequently, and set a larger value for workloads with high load
Resizing blocks can reduce the number of reads and writes of the socket interface
Command-line properties for resizing blocks:-dweblogic.chunksize=n (n=chunksize)
Ensure that the block size is a multiple of the MTU size
Make sure that the block size is a multiple of 8
Resizing a block to the size of the network MTU and the memory of the operating system
At the same time, set the block size on the client and server side JVM for better performance
WebLogic put the block cache in a buffer pool for reuse:-dweblogic.untils.io.chunkpoolsize=n
The default block pool size is 512
A larger block pool should be set up to accommodate applications with more concurrent customers
6. TCP Buffer Backlog (Accept backlog)
The default value is 300, the minimum value is 0, and the maximum value depends on the operating system
If the value of the accept backlog is set too low, most of the connections will be lost or rejected at the client
Error:java.net.ConnectException:Connection Refused:connect
If the value of the accept backlog is set too high, it will cost the server
Should be repeated test, universal principle 4g memory =>accept backlog:8192
7. Adjust the Secure Socket Interface (SSL)
Reduce the number of individual SSL links and I receive
One way to reduce the amount of data for a single SSL link is to use a browser that supports htpp1.1
Transfer SSL processing from the application server to the dedicated SSL accelerator
General principles for improving performance
Designers and coders should understand the use of module resources, interfaces, time, etc.
Minimize large-volume operations and remote calls to the database
Memory operation performance is greater than disk operation, multi-use caching technology
Strictly Manage session Overhead
There are more vertical and horizontal extensions on the architecture.
WebLogic Tuning Notes