Vinh Cao
May 7, 2024
visibility 2785
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

Giving Optimizely 13 Content Types Meaningful Icons and Thumbnails

When working with an Optimizely CMS solution that has evolved over time, it is common to end up with many content types. As the number grows, the...

Pär Wissmark | Sep 16, 2026 |

force-dynamic vs connection() for Optimizely Graph

If you have built an Optimizely CMS SDK site, you already know getContentByPath on a catch-all. This post is about the part that file never says ou...

Chirag Khanna | Sep 16, 2026 |