From 2a6699249322b130265e53ee2b16bb7ecd74f75e Mon Sep 17 00:00:00 2001 From: kjac Date: Mon, 20 Oct 2025 08:43:06 +0200 Subject: [PATCH 1/3] Add documentation for indexing batch size configuration --- .../reference/configuration/indexingsettings.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/17/umbraco-cms/reference/configuration/indexingsettings.md b/17/umbraco-cms/reference/configuration/indexingsettings.md index 66044d8daf7..1ae7d36d172 100644 --- a/17/umbraco-cms/reference/configuration/indexingsettings.md +++ b/17/umbraco-cms/reference/configuration/indexingsettings.md @@ -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 } } } @@ -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 (e.g. 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. From a695eb9aa1118f7966e2907b557def6c3d099a7d Mon Sep 17 00:00:00 2001 From: kjac Date: Mon, 20 Oct 2025 08:49:17 +0200 Subject: [PATCH 2/3] Make the Linter happy --- 17/umbraco-cms/reference/configuration/indexingsettings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/17/umbraco-cms/reference/configuration/indexingsettings.md b/17/umbraco-cms/reference/configuration/indexingsettings.md index 1ae7d36d172..e6b2b3b71ea 100644 --- a/17/umbraco-cms/reference/configuration/indexingsettings.md +++ b/17/umbraco-cms/reference/configuration/indexingsettings.md @@ -29,6 +29,6 @@ In some cases this yields a lot of fields in the index, which can lead to errors ## BatchSize -For large indexing operations (e.g. rebuilding an index), content is loaded from the database and indexed in batches. +For large indexing operations (rebuilding an index, for example), 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. From 71985939641d615a3faa9337b16e9fc708f935bf Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 20 Oct 2025 09:42:36 +0200 Subject: [PATCH 3/3] Update 17/umbraco-cms/reference/configuration/indexingsettings.md --- 17/umbraco-cms/reference/configuration/indexingsettings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/17/umbraco-cms/reference/configuration/indexingsettings.md b/17/umbraco-cms/reference/configuration/indexingsettings.md index e6b2b3b71ea..0d81dc093f3 100644 --- a/17/umbraco-cms/reference/configuration/indexingsettings.md +++ b/17/umbraco-cms/reference/configuration/indexingsettings.md @@ -29,6 +29,6 @@ In some cases this yields a lot of fields in the index, which can lead to errors ## BatchSize -For large indexing operations (rebuilding an index, for example), content is loaded from the database and indexed in batches. +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.