# What are typical memory or cpu intensive workloads?

**URL:** <https://discuss.elastic.co/t/what-are-typical-memory-or-cpu-intensive-workloads/247978>\
**Category:** Elasticsearch\
**Created:** [September 9, 2020, 8:37am UTC](https://discuss.elastic.co/t/what-are-typical-memory-or-cpu-intensive-workloads/247978 "2020-09-09T08:37:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vchalmel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vchalmel/32/11681_2.png) [@vchalmel](https://discuss.elastic.co/u/vchalmel)\
**Post date:** [September 9, 2020, 8:37am UTC](https://discuss.elastic.co/t/what-are-typical-memory-or-cpu-intensive-workloads/247978/1 "2020-09-09T08:37:47Z")

</div>

I would like to get a better understanding of the alternative proposed for elastic-cloud new deployements between "I/O" "CPU" or "memory" optimizations.

What they are, and how the selected hardware is balanced is pretty clear, but the documentation doesn't provide much insight of the use-cases that would better fit each category (except for the high-memory adequation to aggregations).

So I guess my question would be :

- What is a typical "CPU-intensive workload" for elastic ?
- I had the feeling that some of my indices with highly nested mappings run queries better on cpu-intensive than i/o intensive ? Is that accurate ?
- Is there any other case than aggregations (would that include extensive use of kibana ?) for which High-mem is required ?

---

<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:** [October 7, 2020, 8:37am UTC](https://discuss.elastic.co/t/what-are-typical-memory-or-cpu-intensive-workloads/247978/2 "2020-10-07T08:37:47Z")

</div>

Closed on October 7, 2020, 8:37am UTC

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