
Thefollowing example shows native thread pool information as it appears in perfdump:
Native pools:
----------------------------
NativePool:
Idle/Peak/Limit 1/1/128
Work Queue Length/Peak/Limit 0/0/0
my-custom-pool:
Idle/Peak/Limit 1/1/128
Work Queue Length/Peak/Limit 0/0/0
Ifyou have dened additional custom thread pools, they are shown under the Native Pools
headingin perfdump.
Thefollowing table shows the thread pool statistics as they appear in the Admin Console. If you
havenot dened additional thread pools, only the NativePool is shown:
TABLE2–5 ThreadPoolsStatistics
Name NativePool
IdleThreads 1
Threads 1
RequestsQueued 0
PeakRequests Queued 0
Idle/Peak /LimitIdle,listed as Idle Threads in the Admin Console, indicates the number of threads that are
currentlyidle. Peak indicates the peak number of threads in the pool. Limit, listed as Threads in
theAdmin Console, indicates the maximum number of native threads allowed in the thread
pool,and for NativePool is determined by the setting of NativePoolMaxThreads in the
magnus.confle.
Tuning
Youcan modify the maximum threads for NativePool by editing the NativePoolMaxThreads
parameterin magnus.conf. For more information, see “NativePoolMaxThreads Directive” on
page68.
WorkQueue Length /Peak /LimitThesenumbers refer to a queue of server requests that are waiting for the use of a native thread
fromthe pool. The Work Queue Length is the current number of requests waiting for a native
thread,which is represented as Requests Queued in the Admin Console.
UsingMonitoringData to TuneYour Server
SunJavaSystem Web Server 7.0 Update 1 Performance Tuning,Sizing, and Scaling Guide •66