Skip to content

Add documentation for indexing batch size configuration #7527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add documentation for indexing batch size configuration #7527

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2a66992
Add documentation for indexing batch size configuration
kjac Oct 20, 2025
a695eb9
Make the Linter happy
kjac Oct 20, 2025
7198593
Update 17/umbraco-cms/reference/configuration/indexingsettings.md
eshanrnh Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion 17/umbraco-cms/reference/configuration/indexingsettings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,8 @@ This section allows you to configure how content is indexed for Examine.
"Umbraco": {
"CMS": {
"Indexing": {
"ExplicitlyIndexEachNestedProperty": true
"ExplicitlyIndexEachNestedProperty": true,
"BatchSize": 10000
}
}
}
Expand All @@ -25,3 +26,9 @@ When indexing content, each property contained within certain complex editors ar
The complex editors are also indexed to their own separate fields, which then contains "the sum" of all properties contained within.

In some cases this yields a lot of fields in the index, which can lead to errors when performing searches. Changing this setting to `false` can mend that issue. It prevents each contained property from being written to the index in its own field.

## BatchSize

For large indexing operations (such as rebuilding an index), content is loaded from the database and indexed in batches.

Depending on the complexity of your content model, lowering the batch size might speed up these operations.