# Docker Sizing in production

**URL:** <https://discuss.elastic.co/t/docker-sizing-in-production/76022>\
**Category:** Elasticsearch\
**Created:** [February 22, 2017, 11:56am UTC](https://discuss.elastic.co/t/docker-sizing-in-production/76022 "2017-02-22T11:56:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![madhu1512](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@madhu1512](https://discuss.elastic.co/u/madhu1512)\
**Post date:** [February 22, 2017, 11:56am UTC](https://discuss.elastic.co/t/docker-sizing-in-production/76022/1 "2017-02-22T11:56:18Z")

</div>

Any guidelines on hardware sizing for Elasticsearch Docker to run in production?

I am trying to findout what type of instance to choose in AWS? How much memory we need to allocate to Docker Host and how much heap size we need to set for elasticsearch process?

Here is the current config i am using

Host: 8 CPU x 30 GB (m3.2xlarge)  
Docker Host: 4 cpu x 24 GB assigned  
Elasticsearch Heap: 12 GB

-Madhu

---

<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:** [February 24, 2017, 10:14am UTC](https://discuss.elastic.co/t/docker-sizing-in-production/76022/2 "2017-02-24T10:14:53Z")

</div>

We always recommend 50:50 - RAM:HEAP, irrespective of the host/container size.

Bit with a host of that size, I'd just run a single node. If that is what you mean.

---

<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:** [March 24, 2017, 10:14am UTC](https://discuss.elastic.co/t/docker-sizing-in-production/76022/3 "2017-03-24T10:14:56Z")

</div>

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