Two screens show cache usage.
Prerequisites
To use the functionalities described on this page, it must be activated in the administration area configuration screen. The Cache statistics category and the Connection to monitoring database must be filled in. This configuration must be made for the CMS application (back) and the SITE application (front). If you configure only the application CMSyou will not have access to cache statistics.
Dynamic cache statistics
This cache stores page elements (content, services) in RAM. Pages with dynamic elements are thus served more quickly by CMS when they are partially already cached.
This screen displays access statistics for pages and page elements on CMS.
Statistics can be filtered by cache usage context:
- CMS
- Preview
- Online version
- Website
Click on a context to view or hide its statistics.
The statistics displayed on each line are the sum of the tree's sub-elements: for a given page, you can therefore read the statistics not only for the page itself, but also for its sub-pages.
To see the details of a page, open the 'Details' sub-element. The"Cacheable" column represents the percentage of page elements that can be cached, weighted by the number of hits per element: the percentage obtained is therefore comparable to the"Efficiency" column.
An efficiency of 0% is probably synonymous with a deactivated dynamic cache in the general configuration.
Examples of cache usage analysis
Zoom to "index.html" page in preview mode
In this example, the page "index.html" was requested 5 times. Out of 35 page elements, 28 were served by the cache, resulting in 80% cache efficiency.
The page is 100% cacheable, which means that all its elements are cacheable. In detail, these elements are content, service and 5 input data.
Zoom in on the "newsletter.html" page in preview mode
In this example, the page "newsletter.html" was requested 3 times. Out of 24 page elements, 14 were served by the cache, resulting in 58% cache efficiency.
The page is only 88% cached. In fact, in the details of its constituent elements, we can see that a service cannot be cached.
Static cache statistics
This cache stores complete pages (when cacheable as a whole) on hard disk. Pages are served by front-office applications or directly by an http server (such as Apache Httpd).
This screen displays cache usage statistics for the site.
More information can be displayed by clicking on the "Show/Hide Details" button. You'll get detailed statistics for the HTTP server and the frontoffice application: this verifies that the HTTP server is correctly configured to serve the cache directory directly.
The "Cacheable" percentage is weighted by the number of hits, making it comparable to the "Efficiency" column.
Example: zoom in on the "index.html" page
The page "index.html" was requested 6 times from Apache. Of these 6 times, it was taken 3 times from the static cache (hence an efficiency of 50%), and 3 times the request was transmitted to the back-office.
It is possible to have a slight inconsistency between the front and back office figures, as each performs its own "temporization" of the statistics.
Important
Cache statistics are updated every hour.
Back to top