While it would be extremely unusual to hit this possible performance problem, the number of
groups cached in a single ACL cache entry can be tuned with Maximum Groups setting on the
conguration's Performance tab ⇒ Cache sub tab. Or you can use the max-groups-per-user
property of the wadm set-acl-cache-prop command.
The maximum age setting of the ACL cache determines the number of seconds before the cache
entries expire. Each time an entry in the cache is referenced, its age is calculated and checked
against the maximum age setting. The entry is not used if its age is greater than or equal to the
maximum age. The default value is 120 seconds. If your LDAP is not likely to change often, use a
large number for the maximum age. However, if your LDAP entries change often, use a smaller
value. For example, when the value is 120 seconds, the Web Server might be out of sync with the
LDAP server for as long as two minutes. Depending on your environment, that might or might
not be a problem.
Tuning Java Web Application Performance
This section contains information to help you improve the performance of your Java Web
Applications. This section includes the following topics:
■
“Using Precompiled JSPs” on page 78
■
“Using Servlet/JSP Caching” on page 79
■
“Conguring the Java Security Manager” on page 79
■
“Conguring Class Reloading” on page 79
■
“Avoiding Directories in the Classpath” on page 80
■
“Conguring the Web Application’s Session Settings” on page 80
In addition, see the following sections for other tuning information related to the Java Web
Applications:
■
“Java Virtual Machine (JVM) Information” on page 70
■
“JDBC Resource Information” on page 72
Using Precompiled JSPs
Compiling JSPs is a resource-intensive and relatively time-consuming process. By default, the
Web Server periodically checks to see if your JSPs have been modied and dynamically reloads
them; this allows you to deploy modications without restarting the server. The
reload-interval property of the jsp-config element in sun-web.xml controls how often the
server checks JSPs for modications. However, there is a small performance penalty for that
checking.
When the server detects a change in a .jsp le, only that JSP is recompiled and reloaded; the
entire web application is not reloaded.
If your JSPs don't change, you can improve performance by precompiling your JSPs.
TuningJavaWebApplicationPerformance
SunJavaSystemWebServer7.0Update1 PerformanceTuning,Sizing,and ScalingGuide •78