Skip navigation.
Downloads | Product Documentation | Support

Performance Tuning Guide

# Tuning Your Portal Application

One of the most effective ways to tune your portal application is to monitor and adjust the cache settings used.

# Managing Caches

WebLogic Portal provides a single framework for configuring, accessing, monitoring, and maintaining caches. If configured properly, the caches can vastly reduce the time needed to retrieve frequently used data.

Many WebLogic Portal services use preconfigured caches that you can tune to meet your performance needs. Some services use internally configured caches that you cannot configure or access. If you extend or create additional services, you can use the cache framework to define and use your own set of caches.

WebLogic Portal Cache Settings lists caches that might be used by your portal application. Use the list to assist in your tuning. Keep in mind the memory that is available to your system. When modifying the maximum cache sizes also monitor the system memory to determine the effects.

## Using the Portal Administration Tool to Configure Cache Settings

You can use the Service Administration tools within the Portal Administration Tool to configure statically-defined caches. For a list of configurable caches, see WebLogic Portal Cache Settings.

When you configure a cache, you modify its parameters to change its behavior or capability. For example, you can set up a cache to hold only the last 10,000 entries and set the time they can remain in the cache. You can also flush the cache so that all new requests for information come directly from the database.

For instructions on how to configure cache settings, see

http://edocs.bea.com/wlp/docs81/adminportal/help/SA_CacheConfig.html

## Caching with JSP Tags

When you chose to configure caches on individual JSP tags, you can have more control over individual content queries. Although this can be seen as an advantage, remember that when you control caches with coding, any cache change will require more maintenance, depending on the size (amount of code) of your application.

The following content management-related JSP tags include cache-related attributes:

- <cm:search>
- <cm:getNode>
- <pz:contentSelector>
- <pz:contentQuery>

For more information about these JSP tags and their attributes, see http://edocs.bea.com/workshop/docs81/doc/en/portal/taglib/JspWlpOverview.html