
FileCache Entries number, you can improve the accelerator cache utilization by following the
tuninginformation described in “Acceleratable Requests” on page 61 and “Acceleratable
Responses”on page 61.
AcceleratableRequestsThenumber of client requests that were eligible for processing by the accelerator cache. Only
simpleGET requests are processed by the accelerator cache. The accelerator cache does not
processrequests that explicitly disable caching, for example, requests sent when a user clicks
Reloadin the browser and requests that include a query string, that is, requests for URLs that
includea ? character.
Tuning
Tomaximize the number of acceleratable requests, structure your web sites to use static les
whenpossible and avoid using query strings in requests for static les.
AcceleratableResponsesThenumber of times the response to an acceleratable request was eligible for addition to the
acceleratorcache.
Tuning
Whenthe server serves a static le from the le cache, the accelerator cache may be able to cache
theresponse for faster processing on subsequent requests. To maximize performance, you
shouldmaximize the number of responses that are acceleratable. In the default conguration,
allresponses to requests for static les can be cached in the accelerator cache. The following
congurationchanges may prevent a response from being acceleratable:
■ACLsthat deny read access
■Additionaldirectives in the default object of the obj.conf le, including third party plug-ins
■Using<Client> or <If> in the default object of the obj.conf le
■Customaccess log formats
■JavaServlet lters
Tomaximize the number of responses that are acceleratable, avoid such congurations.
AcceleratorHit RatioThenumber of times the response for an acceleratable request was found in the accelerator
cache.
UsingMonitoringData to TuneYour Server
Chapter2 • Tuning Sun Java System Web Server 61