Thedierence between this value and the maximum threads is the number of requests reserved
fornon-native thread requests, such as static HTML and image les. Keeping a reserve and
rejectingrequests ensures that your server continues to ll requests for static les, which
preventsit from becoming unresponsive during periods of very heavy dynamic content load. If
yourserver consistently rejects connections, this value is either set too low, or your server
hardwareis overloaded.
Tuning
Youcan modify the NativePoolQueueSize by editing the NativePoolQueueSize directive in
magnus.conf.

NativePoolMaxThreadsDirective

NativePoolMaxThreadsdetermine the maximum number of threads in the native (kernel)
threadpool.
Ahigher value allows more requests to execute concurrently, but has more overhead due to
contextswitching, so bigger is not always better. Typically, you do not need to increase this
number,but if you are not saturating your CPU and you are seeing requests queue up, then you
shouldincrease this number.
Tuning
Youcan modify the NativePoolMaxThreads by editing the NativePoolMaxThreads parameter
inmagnus.conf.

NativePoolMinThreadsDirective

Determinesthe minimum number of threads in the native (kernel) thread pool.
Tuning
Youcan modify the NativePoolMinThreads by editing the NativePoolMinThreads parameter
inmagnus.conf.
DNS CacheInformation
TheDNS cache caches IP addresses and DNS names. Web Server uses DNS caching for logging
andfor access control by IP address. DNS cache is enabled by default. The following example
showsDNS cache information as displayed in perfdump:
DNSCacheInfo:
------------------
enabled yes
UsingMonitoringData to TuneYour Server
SunJavaSystem Web Server 7.0 Update 1 Performance Tuning,Sizing, and Scaling Guide •68