Skip to content

reword to clarify when people should consider index size #3059

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

Merged
merged 4 commits into from
Sep 22, 2025
Merged

reword to clarify when people should consider index size #3059

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6aa8a13
reword to clarify when people should consider index size
shainaraskas Sep 19, 2025
5fc0b09
clarify when to care about index size
shainaraskas Sep 19, 2025
c165e37
Update deploy-manage/deploy/elastic-cloud/differences-from-other-elas…
shainaraskas Sep 19, 2025
dfc4a34
Merge branch 'main' into srv-index-guidelines
shainaraskas Sep 22, 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
2 changes: 1 addition & 1 deletion ...y-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,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.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.

Expand Down
Loading