Improve lib performance

**Feature request**
It would be great to have filtering for data.

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

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

The issue does not name a file, test, or entry point. Start by locating the library configuration handling and determine how data filtering should behave for production deployments; clarify the filtering semantics and how enable_filtering interacts with existing data flows. Done means the new option defaults to false and filtering works as specified.

Written by the indexing model from the issue text.