Monitor ESI caching

Monitor runtime cache | Summary

Monitor ESI caching

+
Search Tips | Advanced Search

The ESI processor's cache is monitored through the Dynamic Cache Monitor application. In order for the ESI processor's cache to be visible in the cache monitor...

The DynaCacheEsi application must be installed
The esiInvalidationMonitor property must be set to true in plugin-cfg.xml

Point your browser to the Dynamic Cache Monitor application. To get this statistic you need to select Edge Statistics in the Cache monitor navigation bar.

Tip: During our tests, we found that the Edge statistics are only displayed in one of the Dynamic Cache Monitor applications on one of the application servers. So you will need to verify which one is the correct one.

The Edge Statistics could be confused with the Caching Proxy statistics, which is part of IBM WebSphere Edge Components. However, the term Edge Statistics in this case relates to the ESI cache statistics. If you do not see Edge Statistics right away, try clicking the Refresh Statistics button.

Figure 13-19 ESI cache statistics
The following information is available:

ESI Processes Number of processes configured as edge caches.
Number of Edge Cached Entries Number of entries currently cached on all edge servers and processes.
Cache Hits Number of requests that match entries on edge servers.
Cache Misses By URL A cache policy does not exist on the edge server for the requested template.
Note that the initial ESI request for a template that has a cache policy on a WebSphere Application Server results in a miss. Every request for a template that does not have a cache policy on the WebSphere Application Server will result in a miss by the URL on the Edge server.
Cache Misses By Cache ID In this case, the cache policy for the requested template exists on the edge server. The cache ID is created (based on the ID rules and the request attributes), but the cache entry for this ID does not exist.

Note that if the policy exists on the edge server for the requested template, but a cache ID match is not found, the request is not treated as a cache miss.

Cache Time Outs: The number of entries removed from the edge cache, based on the timeout value.
Evictions: The number of entries removed from the edge cache, due to invalidations received from WebSphere Application Server.

If you click the Contents button, you can see the edge content for all processes or for a selected process number.
The example below shows the TopCategoriesDisplay URL, which we made edge cacheable in Caching full pages.

ESI Processes	Number of processes configured as edge caches.
Number of Edge Cached Entries	Number of entries currently cached on all edge servers and processes.
Cache Hits	Number of requests that match entries on edge servers.
Cache Misses By URL	A cache policy does not exist on the edge server for the requested template. Note that the initial ESI request for a template that has a cache policy on a WebSphere Application Server results in a miss. Every request for a template that does not have a cache policy on the WebSphere Application Server will result in a miss by the URL on the Edge server.
Cache Misses By Cache ID	In this case, the cache policy for the requested template exists on the edge server. The cache ID is created (based on the ID rules and the request attributes), but the cache entry for this ID does not exist.