Page API find method performance with large custom field datasets

ProcessWire's Page API provides the find() method to retrieve pages based on specific field criteria. This flexible schema allows fields to be added to templates without immediate database migrations, enabling rapid development of complex content filters.

When scaling to extremely large datasets, there is a concern regarding the efficiency of these queries. Specifically, the interaction between the fluent API interface and the underlying database indexing for custom fields can impact response times as the page count grows.

What are the recommended indexing strategies for custom fields to prevent performance degradation during find() operations? Are there specific configuration limits or API patterns that ensure optimal query execution on high-volume page trees?