# Composite Aggregation Impact on ES Performance

**URL:** <https://discuss.elastic.co/t/composite-aggregation-impact-on-es-performance/289638>\
**Category:** Elasticsearch\
**Created:** [November 18, 2021, 7:30pm UTC](https://discuss.elastic.co/t/composite-aggregation-impact-on-es-performance/289638 "2021-11-18T19:30:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RahulSingh1905](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahulsingh1905/32/97279_2.png) [@RahulSingh1905](https://discuss.elastic.co/u/RahulSingh1905)\
**Post date:** [November 18, 2021, 7:30pm UTC](https://discuss.elastic.co/t/composite-aggregation-impact-on-es-performance/289638/1 "2021-11-18T19:30:45Z")

</div>

The [ES7.x doc](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-composite-aggregation.html) for composite aggregation warns that : “The composite aggregation is expensive. Load test your application before deploying a composite aggregation in production.”

Some context: My team and I are hoping to replace some of our terms aggregation queries with composite aggregation due to high cardinality. We plan to make the shift to composite aggregation and paginate through the results.

Discussion: I'm looking for some insights regarding its impact on overall performance, since I have limited experience with using composite aggregation.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 16, 2021, 7:31pm UTC](https://discuss.elastic.co/t/composite-aggregation-impact-on-es-performance/289638/2 "2021-12-16T19:31:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.