Cache overview page
Key point: An overview of all caches used by PageSeeder.

This page lets administrators view at a glance all persistent caches, including performance metrics and cache utilization. Use this page to diagnose performance issues and manage cache lifecycle

Understanding the cache table

The caching page displays detailed information about each cache in a table format:

  • Name – The identifier for each cache.
  • Expiry policy – How long items remain in the cache:
    • “No Expiry” – Items remain until manually cleared.
    • “TTI of X days” – Time To Idle; items expire after the specified period of inactivity.
  • Size (entries) – Number of items currently stored in the cache.
  • Heap (max entries) – Maximum number of entries that can be stored in memory.
  • Disk (allocated) – Amount of disk space currently used by the cache.
  • Disk (max space) – Maximum disk space allocated for the cache.

A Size (entries) of 0 indicates the cache is empty. This is normal for caches that are populated on-demand, such as account-lockout or authenticator-lockout.

At the bottom of the table, you'll see a TOTAL row summarizing the combined cache statistics. The page also displays the Available disk space in the top right corner.

If the maximum unallocated space exceeds the available disk space, a warning is displayed to let you know this might cause problems.

Monitoring cache health

Monitor cache performance by checking the Size (entries) values against expected
usage patterns:

  • Document cache (xml-documents) – Approximately one entry per document in your system. If this number is unexpectedly low and you're experiencing slow publish or validation operations, the cache might need to be repopulated by re-indexing the server (ideally overnight for large systems).

  • Lockout caches (account-lockout, authenticator-lockout, reset-password-lockout) – These typically show 0 entries, indicating no locked accounts. Higher numbers might indicate security issues or user problems.

  • User details cache (user-details) – Increases with active user sessions. Low values with many active users might indicate cache thrashing.

When diagnosing performance issues, check both the entry count and whether the cache has reached its Heap (max entries) limit, which might indicate the cache needs reconfiguration.

Clearing the cache

Administrators can clear individual caches using the red Clear button next to each cache, or Clear all caches at once using the button at the bottom of the page.

There is usually no reason to clear the cache in PageSeeder. Caches are already configured for the most common scenarios.

Clearing caches might temporarily impact system performance and user experience:

  • Response times might slow until caches are repopulated.
  • Some operations expect populated caches and can take significantly longer.
  • The xml-documents cache in particular can take considerable time to repopulate in systems with many documents.

Consider clearing caches during off-peak hours or scheduled maintenance windows.

Troubleshooting

Disk space warnings

If you see a warning about disk space, this indicates that the maximum allocated cache space exceeds available disk capacity.

To resolve this issue:

  • Reduce cache allocation – Lower the cacheDiskSize global property to allocate less disk space to caches.
  • Free up disk space – Remove unnecessary files or expand storage capacity.

It is extremely rare that all caches reach maximum capacity simultaneously, as several caches remain empty during normal operations. However, it is safer and good practice to ensure that caches aren't configured to use more space than is available.

Cache performance issues

If you suspect cache-related performance problems, check the Size for relevant caches (especially xml-documents), review whether any caches have reached their maximum (if so you can increase the cacheDiskSize global property).

How to find this page

Administration menu >  System administration > Server status > Caching