# Need some advice on cpu core number vs memory for ece allocator

**URL:** <https://discuss.elastic.co/t/need-some-advice-on-cpu-core-number-vs-memory-for-ece-allocator/169242>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [February 20, 2019, 3:31pm UTC](https://discuss.elastic.co/t/need-some-advice-on-cpu-core-number-vs-memory-for-ece-allocator/169242 "2019-02-20T15:31:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rockybean](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rockybean/32/11443_2.png) [@rockybean](https://discuss.elastic.co/u/rockybean)\
**Post date:** [February 21, 2019, 12:30am UTC](https://discuss.elastic.co/t/need-some-advice-on-cpu-core-number-vs-memory-for-ece-allocator/169242/3 "2019-02-21T00:30:36Z")

</div>

Thanks!  
Do you mean below post?

> [@ECE RAM to Storage Ratio](https://discuss.elastic.co/t/ece-ram-to-storage-ratio/101878/10):
>
> @IanGabes The 2 other "override" fields that have proven useful so far are: "resources": { "cpu": { "hard\_limit": true } }, If you set hard\_limit to false then the cluster gets the entire CPU of the host instead of a sub-set determined by its size. Obviously this is not without risk to the overall platform stability "overrides": { "resources": { // (needed for 1.1+) "cpu": { "factor": 1.3 } } }, A safer way of boosting the CPU for a given…

---

_[View the full topic](https://discuss.elastic.co/t/need-some-advice-on-cpu-core-number-vs-memory-for-ece-allocator/169242)._