# Scalability of Elasticsearch in Docker Container with Specific resources

**URL:** <https://discuss.elastic.co/t/scalability-of-elasticsearch-in-docker-container-with-specific-resources/40828>\
**Category:** Elasticsearch\
**Created:** [February 3, 2016, 6:56am UTC](https://discuss.elastic.co/t/scalability-of-elasticsearch-in-docker-container-with-specific-resources/40828 "2016-02-03T06:56:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![masifpak](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@masifpak](https://discuss.elastic.co/u/masifpak)\
**Post date:** [February 3, 2016, 6:56am UTC](https://discuss.elastic.co/t/scalability-of-elasticsearch-in-docker-container-with-specific-resources/40828/1 "2016-02-03T06:56:11Z")

</div>

Dear Geeks

Container Resources : CPU = 2 Cores RAM= 16 GB

Prior we had 2 indexes (Events, Flows) each with 5 shard and 0 replica. We were writing 2000 (1000 Events + 1000 Flows) in Elasticsearch. CPU and RAM utilization kept at about 80-90 % all the time. Second, sometimes translog files increased to 100 GBs. We increased resources but situation remain same. Then I got a webinar of Bay Shanon, then I decided to use one shard in each index being on one node.  
I just want to confirm that can elasticsearch handle the following load in one index with one shard on one node.

One Day Load (Approx.)  
Events: 75 Million Documents = 75 GB FLows: 75 Million Documents = 75GB  
One Month (Approx.)  
Events: 1500 Million = 1500 GB FLows: 1500 Million = 1500 GB

Thanks

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 7, 2016, 2:58pm UTC](https://discuss.elastic.co/t/scalability-of-elasticsearch-in-docker-container-with-specific-resources/40828/2 "2016-02-07T14:58:19Z")

</div>

75M/day is about 900/s. My hunch is that it might be to much a two-core node, but you should try it out yourself. It depends on your specific hardware, your documents, your mappings, and so on.

---

<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:** [July 5, 2017, 11:18pm UTC](https://discuss.elastic.co/t/scalability-of-elasticsearch-in-docker-container-with-specific-resources/40828/3 "2017-07-05T23:18:22Z")

</div>

Closed on July 5, 2017, 11:18pm UTC