Cache stats

OpenKM takes advantage of cached objects for fast retrieval of data.

For example, the users and roles lists, when the application is configured to work with LDAP, are cached to reduce the 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

Also, cache can be used to collect data useful to detect configuration parameter changes needed to improve 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 in the cache disk.	true
Disc missed	Number of failed queries in the cache disk.	true
Disc objects	Number of objects in the cache disk.	false
Action	Cleans cached objects.	Not applicable.