Performance Tuning for Content Manager

272 Performance Tuning for Content Manager

Our recommendation

Set this value high to get the maximum performance. A good starting value is

100. Monitor your system using Tivoli Performance Viewer to see whether this

value is adequate for your environment.

9.5.6 URL invocation cache

The invocation cache holds information for mapping request URLs to servlet

resources. A cache of the requested size is created for each thread. The number

of threads is determined by the Web container maximum thread size setting. The

default size of the invocation cache is 50. If more than 50 unique URLs are

actively being used (each JavaServer Page is a unique URL), you should

increase the size of the invocation cache.

Default values

50

How to view or set

1. In the administrative console, click Servers → Application servers and

select the application server you are tuning.

2. Under Additional Properties, click Process Definition.

3. Under Additional Properties, click Java Virtual Machine.

4. Under Additional Properties, click Custom Properties.

5. Specify InvocationCacheSize in the Name field and the size of the cache in

the Value field. You can specify any number higher than zero for the cache

size. Setting the value to zero disables the invocation cache.

6. Click Apply and then Save to save your changes.

7. Stop and restart the application server.

Our recommendation

Start with a value of 50. Monitor your system and increase this value as needed.

For example, if more than 50 unique URLs are actively being used (each JSP is a

unique URL), consider increasing this value.

Note: A larger cache uses more of the Java heap, so you might need to

increase maximum Java heap size. For example, if each cache entry requires

2 KB, maximum thread size is set to 25, and the URL invocation cache size is

100 then 5 MB of Java heap is required.