120 likes | 361 Views
WEBLOGIC SERVER. TUNING. TOPICS. Core Server JDBC Tuning JVM Tuning OS Tuning. Core Server. Enable Native IO Tuning Chunk size also reduces the socket reads/writes Set a smaller chunk size for high frequency small payload workloads
E N D
WEBLOGIC SERVER TUNING
TOPICS • Core Server • JDBC Tuning • JVM Tuning • OS Tuning
Core Server • Enable Native IO • Tuning Chunk size also reduces the socket reads/writes • Set a smaller chunk size for high frequency small payload workloads • Set the chunk size at both client and server side to increase the performance • Tune the chunk size to match the network MTU size and operating system memory page size for better performance • Ensure that chunk size is multiple of 8 as well as MTU size • Chunks are pooled to prevent allocation cost (-Dweblogic.utils.io.chunkpoolsize=n) • By default it is 512, you should set a large pool size to accomodate workloads with many concurrent clients.
JDBC Tuning • JDBC Tuning: • Use Oracle thin driver • Disable Shrink frequency in Production make it as 0 • Disable Test connections on Reserve and Test Frequency parameters • Enable Row prefetching • Use statement caching • Pinned to thread enabling improves the perforrmance
JVM • To see a detailed behaviourog GC, use the –verboseGC option • Set –Xms equal to –Xmx to avoid the need to grow heap • For optimum performance, set –Xmn to be one fourth of the value of –Xmx • -Xmn = New Generation Size, -Xms= Initial Total Java Heap, -Xmx = Maximum Total Java Heap
OS Tuning • Contact your OS Administrator
Thank You Q&A ?