Overview

The Caches option within the Admin Console allows administrators to view information about the current and previous states of various caches within the server. Caches provide quick access to frequently used data, and reduce the number of database queries and other requests that the server needs to make. Caches are used to improve overall performance by reusing the same data multiple times, at the expense of using more memory. Limits on the number of objects that can be cached ensure a reasonable tradeoff.

Cache Information

The page enumerates the caches that are in use within the server. Each holds a different kind of information, and may have its own limit on the number of objects it can hold and how long they might be stored in the cache. The Get column shows how many times that code has tried to get an object from the cache. The Put column shows how many times an item has been put in the cache. The Max and Current Size columns show the maximum number of objects held in the cache since the server started, and the current number of objects in the cache, respectively.

Caches that have reached their size limit are indicated separately, and may be good candidates for a larger cache size.

The full information on this page can be analyzed to help tune server performance, typically by LabKey staff.