Cache stats

OpenKM takes advantage of cached objects for fast data retrieval.

Tip

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

The associated cached names for LDAP are:

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

Also, the cache can be used to collect data. This is useful to find out the configuration parameter changes needed for better application perfomance. 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 hists Disc missed 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 missed	Number of failed queries in cache memory.	true
Memory objects	Number of objects in cache memory.	false
Disc hits	Number of successful queries in cache disk.	true
Disc missed	Number of failed queries in cache disk.	true
Disc objects	Number of objects in cache disk.	false
Action	Clean cached objects.	Not applicable.

Clean all cache

• On the right top click on the Reset all button.

Refresh cache stats

• On the top right click on the Refresh icon.

Enable cache stats audit trail

• On the top right click on  Enable cache audit trial button.

Enables the fields stats:

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

Disable cache stats audit trail

• On top right click on the Disable cache audit trial button.

Disable the fields stats:

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