Apr 3, 2023
(2 votes)

Improve performance by enabling language routing on search requests

In Find 13, we introduced language routing on indexing to improve indexing performance for indexes setup with multiple languages.

With the release of Find 13.4.9, we further introduced language routing on query time. We recommend moving up to 13.5.7 due to other bug fixes. This feature is also available in .NET flavours: 14.2.4 and 15.0.3

This feature enables passing the query only to the specific language index, rather than having all language indexes process the query even though most of them would only respond with 0 hits as we're usually filtering on language properties in the index.

Since 13.5.1 this feature is disabled by default.

To enable this feature, there are a few steps to follow:

  1. Ensure that you explicitly or implicitly set the language for your query.
    You typically achieve this by using one of the following approaches:
    .Search<type>(language) or .UnifiedSearch(language)
    Alternatively, you can rely on the extensions provided by Episerver.Find.CMS and use
    .UnifiedSearch() or .UnifiedSearchFor()
    which will automatically set the preferred culture if you don't specify one. Be careful not to use the Episerver.Find extensions, as they do not resolve language.

  2. You can verify that everything is working correctly by checking the analyzer set in the JSON for the request against the _search. 
    It should say analyzer:[language]. If you are using .UsingSynonyms() it should say analyzer: synonym_[language_code].

  3. If you are using CMS 11, you can do this in the web.config file by adding the following:
        <add key="episerver:EnableLanguageRoutingInSearchRequest" value="true"/>
    If you are using CMS 12, you can do this in the appsettings.json file by adding the following:
    "EPiServer": {
        "Find": {

Note that if you have custom InField extension that makes it possible to query fields for multiple language fields, language routing query time cannot be used.

Our tests have shown a decrease in response times of around 25% for queries with language routing enabled. 
However, this improvement may vary depending on your implementation, the number of languages enabled on the index, and the data indexed.

Find versions that support language routing on search requests

Apr 03, 2023


Eric Petersson
Eric Petersson Apr 4, 2023 06:16 AM

Cool! When updating to Find in .NET Framework I get that the packages are based on EPiServer.Cms 11.20.17, which is not availble from the nuget feed. 

Is there a planned release date when it will be available?

dada Apr 4, 2023 07:25 AM

Hi Eric,

Thanks for the feedback. I assume you mean 13.5.7. I will check with the dev team and get back to you.

Eric Petersson
Eric Petersson Apr 4, 2023 07:32 AM

Hi again, the EPiServer.Cms 11.20.17 version

Please login to comment.
Latest blogs
IDX21323 - RequireNonce is true, Nonce was null

We have multiple clients configured with Azure Active Directory (Microsoft Entra) for requiring authentication when accessing their website. The...

David Drouin-Prince | Oct 1, 2023 | Syndicated blog

Minimum Detectable Effect in Optimizely Web Experimentation

Understanding Minimum Detectable Effect Minimum Detectable Effect (MDE) is a core statistical calculation in Optimizely Web Experimentation. In...

Matthew Dunn | Oct 1, 2023 | Syndicated blog

Configured Commerce - Introduction to Long-Term Support (LTS) Releases

First off, for those who have not had a chance to meet me yet, my name is John McCarroll, and I am the Technical Product Manager for the Optimizely...

John McCarroll | Sep 29, 2023

Auto-translate with OpenAI in Optimizely CMS

You can now auto-translate content using your favorite online AI service, inside the old trustworthy Episerver.Labs.LanguageManager!

Tomas Hensrud Gulla | Sep 29, 2023 | Syndicated blog

Vulnerability in CMS 12 shell module configuration

Introduction A potential security vulnerability has been identified in Optimizely CMS 12, triggered by a certain shell module configuration. To be...

Magnus Rahl | Sep 28, 2023

AI-Assistant: The 'Change Tone' Shortcut

The AI-Assistant for Optimizely is constantly evolving, adjusting, and transforming to meet your digital needs, providing a cutting-edge advantage...

Luc Gosso (MVP) | Sep 27, 2023 | Syndicated blog