Cache stats

OpenKM uses cached objects for fast data retrieval.

Tip

For example, the users and roles lists, when the application is configured to work with LDAP, are cached to reduce traffic between the application and the LDAP server.

The associated cached names for LDAP are:

• com.openkm.cache.ldapPrincipalAdapter.general
• com.openkm.cache.ldapPrincipalAdapter.name

The cache can also be used to collect data useful for identifying configuration parameter changes needed for better application performance. For this purpose, the application comes with a cache audit trail.

Cache stats are shown in a table structure:

Cache name Hits Misses Objects Memory hits Memory objects Disc hits Disc misses Disc objects Action

Field	Description	Audit trail required
Cache name	Unique class name of the cached class.	Not applicable.
Hits	Number of successful queries.	true
Misses	Number of failed queries.	true
Objects	Number of cached objects.	false
Memory hits	Number of successful queries in cache memory.	true
Memory misses	Number of failed queries in cache memory.	true
Memory objects	Number of objects in cache memory.	false
Disc hits	Number of successful queries on the cache disk.	true
Disc misses	Number of failed queries on the cache disk.	true
Disc objects	Number of objects on the cache disk.	false
Action	Clean cached objects.	Not applicable.

Clear all caches

• At the top right, click on Reset all button.

Refresh cache stats

• At the top right, click on Refresh icon.

Enable cache stats audit trail

• At the top right, click on Enable cache audit trail button.

Enables the field stats:

• Hits.
• Misses.
• Memory Hits.
• Memory misses.
• Memory objects.
• Disc hits.
• Disc misses.

Disable cache stats audit trail

• At the top right, click on Disable cache audit trail button.

Disables the following field stats:

• Hits.
• Misses.
• Memory Hits.
• Memory misses.
• Memory objects.
• Disc hits.
• Disc misses.