Network Connections Optimizing Network Connections

Oracle Web Cache Performance Tuning 10-9 embedding application session IDs. To resolve this, create your ESI pages with variables. Because variables can resolve to different pieces of request information or response information, the uniqueness of templates and fragments can be significantly reduced. This, in turn, results in better cache hitmiss ratios.

10.6 Optimizing Response Time

If you have not configured the application Web server or the cache correctly, response time may be slower than anticipated. This section summarizes much of the information presented in this chapter. If the application Web server is responding more slowly than expected or if the application Web server is not responding to requests from the cache because it has reached its capacity, check the application Web server and Oracle Web Cache settings. First, check the following: ■ Caching rules: Ensure that you are caching the appropriate objects. Are there popular objects that you should cache but are not caching? Use the Popular Requests page Monitoring Popular Requests to see a list of the most popular requests and to check that those objects are being cached. ■ Priority rankings of the caching rules: Give frequently accessed non-cacheable documents a higher priority than cacheable documents. Give frequently accessed cacheable documents the lowest priority. Note that parsing of caching rules may be resource-intensive if a large number of rules are defined. ■ Compression: If the network is a bottleneck for the client, compressing documents as they are cached can relieve some of the congestion on the network because compressed documents are smaller. Then, check the following: The application Web server configuration, particularly the MaxClients, KeepAlive, KeepAliveTimeout, and MaxKeepAliveRequests settings. The MaxClients limit on the application Web server should be greater than or equal to the application Web server capacity as set through the Oracle Web Cache Manager. The application Web server capacity as set using the Origin Servers page Origin Servers, Sites, and Load Balancing Origin Servers of the Oracle Web Cache Manager. See the Oracle Fusion Middleware Administrators Guide for Oracle Web Cache for information about setting application Web server capacity. Then, if the application Web server is still busier than anticipated, it may mean that the cache cannot process the requests and is routing more requests to the application Web server. Check the following Oracle Web Cache settings in the Oracle Web Cache Manager: ■ The number of cache connections. Check Maximum Incoming Connections in the Resource Limits page Properties Resource Limits. ■ The memory size for the cache. Check Maximum Cache Size in the Resource Limits page Properties Resource Limits. ■ The cache cluster capacity. In a cache cluster, if cluster capacity is too low, a cache may not receive a response for owned content from a peer cache in the specified interval. As a result, the request is sent to the application Web server. Check Capacity in the Clustering page Properties Clustering. See the Oracle Fusion Middleware Administrators Guide for Oracle Web Cache for more information. 10-10 Oracle Fusion Middleware Performance and Tuning Guide If the settings for the application Web server and Oracle Web Cache are set correctly, but the response times are still higher than expected, check system resources, especially: ■ Network bandwidth ■ CPU usage

10.7 Optimizing Performance with Oracle ADF

Consider the following configuration options for optimizing Oracle Web Cache performance with Oracle ADF Rich Client Applications: ■ After you configure the Maximum Cache Size setting in the Resource Limits page of Oracle Web Cache Manager, use a simulated load or an actual load to monitor the cache to see how much memory is actually used. Verify that any additional memory usage does not result in the host swapping memory to disk, as this may impact performance. ■ Personalization and compression rules for all sites include the following: – Images should be cached but not compressed – CSS files should be both cached and compressed for all request types – JS files should be both cached and compressed for all request types – HTML files should be both cached and compressed – SWF files should be cached but not compressed – Add a rule to compress but not cache .jspx files for all GET and POSTS – Add a rule to compress but not cache \.jspx. files for all GET and POSTS – Add a rule to compress but not cache adw\.jspx for all request types – Add a rule not to compress and not cache profiling.js for all request types For more detail on setting cache and compression rules, see Caching and Compressing Content, in Oracle Fusion Middleware Administrators Guide for Oracle Web Cache.