Suitablemaximum threads values range from 100-500, depending on the load. Maximum
Threadsrepresents a hard limit for the maximum number of active threads that can run
simultaneously,which can become a bottleneck for performance. The default value is 128.
Thethread pool minimum threads is the minimum number of threads the server initiates upon
startup.The default value is 16.
Note– When conguring Web Server to be used with the Solaris Network Cache and
Accelerator(SNCA), setting the maximum threads and the queue size to 0 provides better
performance.Because SNCA manages the client connections, it is not necessary to set these
parameters.These parameters can also be set to 0 with non-SNCA congurations, especially for
casesin which short latency responses with no keep-alives must be delivered. It is important to
notethat the maximum threads and queue size must both be set to 0.
Forinformation about using SNCA, see “Using the Solaris Network Cache and Accelerator
(SNCA)”on page 91.

Tuning

Youcan increase your thread limits in the Admin Console by editing the Maximum Threads
eldon the conguration's Performance tab ⇒HTTP tab, under Thread Pool Settings. In the
command-lineinterface, use the wadm set-thread-pool-prop command's max-threads
property.The default is 128.
FileCache Information (Static Content)
Thecache information section provides statistics on how your le cache is being used. The le
cachecaches static content so that the server handles requests for static content quickly. The le
cachecontains information about les and static le content. The le cache also caches
informationthat is used to speed up processing of server-parsed HTML. For servlets and JSPs,
otherkinds of caching are used.
Forsites with scheduled updates to content, consider shutting down the cache while the content
isbeing updated, and starting it again after the update is complete. Although performance slows
down,the server operates normally when the cache is o.
Forperformance reasons, Web Server caches as follows:
■Forsmall les, it caches the content in memory (heap).
■Forlarge les, it caches the open le descriptors (to avoid opening and closing les).
Thefollowing is an example of how the cache statistics are displayed in perfdump:
CacheInfo:
------------------
File Cache Enabled yes
UsingMonitoringData to TuneYour Server
Chapter2 • Tuning Sun Java System Web Server 59