Access Statistics
Access Statistics Windows
The ratio cacheHits:cacheMiss indicates how well the cache server can respond to document accesses. If the counter cacheMiss is higher than cacheHits, performance must be poor. This may be due to the following reasons:
-
Cache is too small, and/or
-
Stored documents are not requested again often enough.
With counters cacheDelete (number of displaced documents) and cacheDeletedBytes you can establish if the size of the cache is too small. The total size of the cache is specified in the counter cacheMaxSize in bytes. Counter cacheCurrentSize indicates the current size of the cache.
Access Statistics Unix
Cache Requests: cacheRequests
Cache Hits: cacheHits
Counter contentServerRequests is the difference between the values of cacheRequests and cacheHits. In addition, unsuccessful content server requests are logged in a separate counter (contentServerBadRequests).
reorgPasses counts how often the cache has to be reorganized (documents displaced). reorgFreeK specifies how many kilobytes are displaced during the reorganization.
Counter reorgProcsFS specifies how many processes are currently occupied with the reorganization of the file system.
reorgPidDB is not a counter. It specifies the process ID of the process that is currently reorganizing the database.
