From 4328d0c2423ff28c6a416ae4db44e8880a29f16b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Mon, 26 Jun 2023 11:09:18 +0200 Subject: [PATCH] [DOCS] Adjusts the note about minimum recommended node size on the ELSER tutorial page (#97083) Co-authored-by: David Roberts --- .../search-your-data/semantic-search-elser.asciidoc | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/reference/search/search-your-data/semantic-search-elser.asciidoc b/docs/reference/search/search-your-data/semantic-search-elser.asciidoc index 93f7494a01aa4..4309af2e44ed6 100644 --- a/docs/reference/search/search-your-data/semantic-search-elser.asciidoc +++ b/docs/reference/search/search-your-data/semantic-search-elser.asciidoc @@ -29,8 +29,13 @@ in your cluster. Refer to the deploy the model. NOTE: The minimum dedicated ML node size for deploying and using the ELSER model -is 4 GB. This is a minimum and better performance can be achieved by using -bigger ML nodes. +is 4 GB in Elasticsearch Service if +{cloud}/ec-autoscaling.html[deployment autoscaling] is turned off. Turning on +autoscaling is recommended because it allows your deployment to dynamically +adjust resources based on demand. Better performance can be achieved by using +more allocations or more threads per allocation, which requires bigger ML nodes. +Autoscaling provides bigger nodes when required. If autoscaling is turned off, +you must provide suitably sized nodes yourself. [discrete]