Find _config requests

The French say “jamais deux sans trois”. If something happens twice, it will happen again.

Twice I have seen questions about why Episerver Find performs multiple/repeated requests to the Find index for its configuration (_config) when working to minimize the number of queries.

Sometimes these requests are spotted when using a Performance Profiler such as the excellent one from RedGate or when using the equally excellent HTTP Debugger called Fiddler from Eric Lawrence now owned by Telerik:

Find _config requests captured in Fiddler

(To set Fiddler up to catch Find requests from your web application, follow Telerik’s guide for .NET processes running under a different user account).


The SearchClient of Episerver Find is designed to be a singleton. If you do not use the SearchClient as such, each time it is created it will need to query the index for its settings. You will have one call for each time you create a SearchClient, and this _config request is included into the throttle_limit that the service enforces.

Always use SearchClient.Instance  or a similar construct to access an instance of the SearchClient class.

Why do a _config request?

It augments the SearchClient with a few settings, such as the maximum request size, the configured throttle limitation, the API version and the maximum number of documents that the index may contain. If any of these settings are changed, the application needs to refresh its singleton instance. It happens when the application restart.

followed by some JSON:


Leave a Reply

Your email address will not be published. Required fields are marked *