0

I'm using a terms aggregation in Elasticsearch and have a question about the size parameter.

If I set size: 1000 in the aggregation, but the actual number of buckets returned is always much lower—say around 150—does this have any impact on memory usage or performance?

Is it more efficient to set size closer to the expected number of buckets, or is there no real penalty for setting it higher than necessary?

Looking to understand the trade-offs here.

Improve this question
Related questions
3413
Improve INSERT-per-second performance of SQLite
4
Elasticsearch "size" value not working in terms aggregation with partitions
19
Build a Kibana Histogram with buckets dynamically created by ElasticSearch terms aggregation
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.