Optimize controllers for large datasets

**Feature request**
It would be great to have caching for lib.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_caching` with default `false`.

Start by locating the lib directory and the existing controller and configuration entry points. Trace how large datasets are handled and how configuration options are defined, then determine the expected caching behavior for enable_caching with its default set to false. Done means the option is supported and caching improves the stated production use case without changing the default behavior.

Written by the indexing model from the issue text.