# Elastic cloud cpu scaling

**URL:** <https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401>\
**Category:** Elasticsearch\
**Created:** [November 23, 2020, 8:32pm UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401 "2020-11-23T20:32:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)\
**Post date:** [November 23, 2020, 8:32pm UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/1 "2020-11-23T20:32:04Z")

</div>

When increasing the ram on an instance in elastic cloud, does this increase the cpu cores to that instances as well as increase the credit?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 24, 2020, 12:12am UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/2 "2020-11-24T00:12:31Z")

</div>

Take a look at [https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html#ec\_cpu\_usage](https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html#ec_cpu_usage) and [https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html#ec\_cpu\_credits](https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html#ec_cpu_credits), which you may have already seen I am guessing.

Ultimately, it's all based on the underlying resources of the hardware it runs on. That means it's not a simple X size node is is Y cores.

---

<div class="post-metadata">

**Author:** ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)\
**Post date:** [November 24, 2020, 9:09am UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/3 "2020-11-24T09:09:41Z")

</div>

Hi,

For a given tier ie hot. Had an issue where 2 x 4gb nodes received a huge amount of data over the weekend and several days later even after a reboot they were still using near 100% cpu and all of the credits. Upgraded to 8gb and within 15 mins of starting the cpu load was \<30% and credits recovered.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 24, 2020, 8:05pm UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/4 "2020-11-24T20:05:55Z")

</div>

Larger instances do get more cores, just had that clarified.

---

<div class="post-metadata">

**Author:** ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)\
**Post date:** [November 25, 2020, 12:50pm UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/5 "2020-11-25T12:50:42Z")

</div>

@warkolm  
Thats excellent, its what hoped i observed and not just a fluke 2nd restart clearing the issue.

Thanks

---

<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 23, 2020, 12:50pm UTC](https://discuss.elastic.co/t/elastic-cloud-cpu-scaling/256401/6 "2020-12-23T12:50:52Z")

</div>

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