Vinh Cao
May 7, 2024
  2426
(2 votes)

Search & Navigation: Indexing job new features

From Episerver.Find version 16.1.0, we introduced some new features that make the indexing job in CMS more flexible and efficient:

  • Support continuous indexing job. In case the job has been crashed, you can restart and it will continue indexing progress from the last content that has successfully indexed.
  • Allows configuration of the maximum concurrent background tasks used during the indexing job.
  • Allows configuration of how many queue items are loaded per loop when using the continuous indexing job. With this configuration and the maximum concurrent background tasks, you can adjust the job to balance CPU/memory allocations and indexing speed rate as well.

How to enable the new continuous indexing job and other new features

We have some new options that need to be added to appsettings.json file to enable the new continuous indexing job and other new features:

{
    ...
    "EPiServer": {
        "Find": {
            "DefaultIndex": "your_index",
            "ServiceUrl": "https://demo.find.episerver.net/your_key",
            "Cms": {
                "EnableContinuousContentIndexingJob": true, // to enable the new continuous indexing job
                "IndexingJobMaxThread": 4, // to configure the maximum concurrent background tasks 
                "IndexingJobQueueItemLoadMultiplier": 4 // to configure how many queue items are loaded per loop 
            }
        }
    },
    ...
}

You can also learn how to use these new features on our document. Please check it out.

May 07, 2024

Comments

Please login to comment.
Latest blogs
From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026