From 6aa8a13c95a3efd04017a26e8fbef8f9cd09839b Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Fri, 19 Sep 2025 16:31:24 -0400 Subject: [PATCH 1/3] reword to clarify when people should consider index size --- .../differences-from-other-elasticsearch-offerings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 7c115fb066..012f2cf734 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -160,7 +160,7 @@ To ensure optimal performance in Serverless Elasticsearch projects, follow these | **General search (non data-stream)** | 300GB | General purpose | | **Other uses (non data-stream)** | 600GB | General purpose | -For large datasets that exceed the recommended maximum size, consider splitting your data across smaller indices and using an alias to search them collectively. +If you expect that you will have large datasets that exceed the recommended maximum size, consider creating multiple smaller indices that you can query using an [alias](/manage-data/data-store/aliases.md), or configuring [data stream lifecycle](/manage-data/lifecycle/data-stream) to prevent data streams from growing larger than the maximum size. These recommendations do not apply to indices using better binary quantization (BBQ). Refer to [vector quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for more information. From 5fc0b09063ddc0865b2648b5f203129de0f2cfe5 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Fri, 19 Sep 2025 16:36:55 -0400 Subject: [PATCH 2/3] clarify when to care about index size --- .../differences-from-other-elasticsearch-offerings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 012f2cf734..0b7ccf4b6c 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -160,7 +160,7 @@ To ensure optimal performance in Serverless Elasticsearch projects, follow these | **General search (non data-stream)** | 300GB | General purpose | | **Other uses (non data-stream)** | 600GB | General purpose | -If you expect that you will have large datasets that exceed the recommended maximum size, consider creating multiple smaller indices that you can query using an [alias](/manage-data/data-store/aliases.md), or configuring [data stream lifecycle](/manage-data/lifecycle/data-stream) to prevent data streams from growing larger than the maximum size. +If you expect that you will have large datasets that exceed the recommended maximum size, consider creating multiple smaller indices that you can query using an [alias](/manage-data/data-store/aliases.md), or configuring [data stream lifecycle](/manage-data/lifecycle/data-stream) to prevent data streams from growing larger than the maximum size. You should design your indexing and data lifecycle strategy with the size and growth of your data in mind. These recommendations do not apply to indices using better binary quantization (BBQ). Refer to [vector quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for more information. From c165e375c80a123675df3f83cef2b18794350f25 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Fri, 19 Sep 2025 16:54:56 -0400 Subject: [PATCH 3/3] Update deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md --- .../differences-from-other-elasticsearch-offerings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 0b7ccf4b6c..fc9efe35f0 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -160,7 +160,7 @@ To ensure optimal performance in Serverless Elasticsearch projects, follow these | **General search (non data-stream)** | 300GB | General purpose | | **Other uses (non data-stream)** | 600GB | General purpose | -If you expect that you will have large datasets that exceed the recommended maximum size, consider creating multiple smaller indices that you can query using an [alias](/manage-data/data-store/aliases.md), or configuring [data stream lifecycle](/manage-data/lifecycle/data-stream) to prevent data streams from growing larger than the maximum size. You should design your indexing and data lifecycle strategy with the size and growth of your data in mind. +If you expect that you will have large datasets that exceed the recommended maximum size, consider creating multiple smaller indices that you can query using an [alias](/manage-data/data-store/aliases.md), or configuring [data stream lifecycle](/manage-data/lifecycle/data-stream.md) to prevent data streams from growing larger than the maximum size. You should design your indexing and data lifecycle strategy with the size and growth of your data in mind. These recommendations do not apply to indices using better binary quantization (BBQ). Refer to [vector quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for more information.