The Memory Usage page within the Admin Console
shows information about current memory utilization within the LabKey Server process. This information can be useful in identifying problematic settings or processes.
The top section of the page shows graphs of the various memory spaces within the Java Virtual Machine, including their current utilization and their maximum size. The Heap and Metaspace sections are typically the most likely to hit their maximum size.
Detailed stats about the pools available. Their initial size, amount used, amount committed, and max setting. This section also includes a list of system property names and their values.
When the server is running with Java asserts enabled (via the -ea parameter on the command-line), the bottom of the page will show key objects that are tracked to ensure that they are not causing memory leaks. This is not a recommended configuration for production servers.
The links at the top of the page allow an administrator to clear caches and garbage collect (gc):
- Clear caches, gc and refresh
- Gc and refresh
Garbage collection will free memory claimed by unused objects. This can be useful to see how much memory is truly in use at a given point in time.
LabKey develops, tests, and deploys using the default Java garbage collector. Explicitly specifying an alternative garbage collector is not recommended.