BEA WebLogic Server Tuning Guide

25
$SYSTEM.SYSTEM.ZSYSCFG
KMS.SWAPFILE = 0 $SWAP01.SWAP1.CPU00
KMS.SWAPFILE = 1 $SWAP01.SWAP1.CPU01
KMS.SWAPFILE = 0 $SWAP01.SWAP2.CPU00
KMS.SWAPFILE = 1 $SWAP01.SWAP2.CPU01
KMS.SWAPFILE = 0 $SWAP01.SWAP3.CPU00
KMS.SWAPFILE = 1 $SWAP01.SWAP3.CPU01
KMS.SWAPFILE = 2 $SWAP23.SWAP1.CPU02
KMS.SWAPFILE = 3 $SWAP23.SWAP1.CPU03
KMS.SWAPFILE = 2 $SWAP23.SWAP2.CPU02
KMS.SWAPFILE = 3 $SWAP23.SWAP2.CPU03
KMS.SWAPFILE = 2 $SWAP23.SWAP3.CPU02
KMS.SWAPFILE = 3 $SWAP23.SWAP3.CPU03
KMS.SWAPFILE = 4 $SWAP45.SWAP1.CPU04
KMS.SWAPFILE = 5 $SWAP45.SWAP1.CPU05
KMS.SWAPFILE = 4 $SWAP45.SWAP2.CPU04
KMS.SWAPFILE = 5 $SWAP45.SWAP2.CPU05
KMS.SWAPFILE = 4 $SWAP45.SWAP3.CPU04
KMS.SWAPFILE = 5 $SWAP45.SWAP3.CPU05
NSK-NSK-status su cpu,pin,detail
SYSTEM : \SYSNAME LOGTIME : August 18, 2003 11:09:04
TYPE : (E=Extensible S=Shared O=Owner)
(CPU Page size is 16384 Bytes)
_____________________________________________________________________________
Process Pri User-ID Program File Name
C,pin 150 nnn,mm $DATA01.ZYQ00000.Z0007DAS
KMSF-BACKED SEGMENTS: (Process Space Guarantee = 1424KB)
-----------------------------------------------------------------------------
SEG-ID TYPE SIZE RESERVATION
KBYTE PAGES KBYTE
-----------------------------------------------------------------------------
2101 8B 1 16
2100 8B 1 16
Heap+Global+SRL+Stack 281MB 18023 281MB
-----------------------------------------------------------------------------
TOTAL 18023 281MB
FILE-BACKED SEGMENTS: None
_____________________________________________________________________________
As shown, this process currently uses 281MB of swap-space and has two segments allocated. Incidentally, this JVM
was started with a heap size of 128 MB, which shows that apart from the Java heap, there is a requirement of
roughly 153 MB for process specific data. Note that this swap usage must be checked at a steady state where all
the native components used by a JVM have been fully initialized and executing to get the right value for swap
usage of a JVM process. Compared to WLS 7.0 and NSJ 3.1, this is a steep increase in the JVM swap usage.
Several factors contribute to this. The JVM proper has grown bigger with more memory requirements and the
hotspot compiler also needs additional memory for its internal use.
Incidentally, the WLS instance for which the swap usage above was obtained was not configured with SQL/MX
connection pools. SQL/MX and associated native components have large heap requirements, which also must be
considered as part of the overall configuration.
WebLogic Server provides a set of attributes to configure the frequency and sample size to check for low memory
situations and force a garbage collection. WebLogic Server can be configured with threshold values for detecting