# Advice for production configuration

**URL:** <https://discuss.elastic.co/t/advice-for-production-configuration/6497>\
**Category:** Elasticsearch\
**Created:** [January 25, 2012, 3:49pm UTC](https://discuss.elastic.co/t/advice-for-production-configuration/6497 "2012-01-25T15:49:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shane\_Witbeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shane_witbeck/32/2803_2.png) [@Shane\_Witbeck](https://discuss.elastic.co/u/Shane_Witbeck)\
**Post date:** [January 25, 2012, 3:49pm UTC](https://discuss.elastic.co/t/advice-for-production-configuration/6497/1 "2012-01-25T15:49:52Z")

</div>

I have a single index with ~1M documents at 3.2GB total. During development  
I've been using a single ES node with default VM and ES settings on a box  
with 4GB of RAM. I've been happy with performance (most queries under  
100ms) but haven't tested this setup under load. I'm preparing to start a  
phased roll out to production and need advice about what tweaks I should  
make. Production traffic should be relatively low.

Here is some more information:

cluster health: [https://gist.github.com/1676855](https://gist.github.com/1676855)

cluster state: [https://gist.github.com/1676864](https://gist.github.com/1676864)

cluster nodes: [https://gist.github.com/1676870](https://gist.github.com/1676870)

status: [https://gist.github.com/1676878](https://gist.github.com/1676878)

What, if anything, should I do as a starting point to prepare for  
production use?

Thanks.

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [January 25, 2012, 4:49pm UTC](https://discuss.elastic.co/t/advice-for-production-configuration/6497/2 "2012-01-25T16:49:59Z")

</div>

If things are good, and dev is similar to production, then go for it. I would suggest setting the same memory MIN/MAX memory value. By default, min is 256m and max is 1g, so set both to 1g.

On Wednesday, January 25, 2012 at 5:49 PM, Shane Witbeck wrote:

> I have a single index with ~1M documents at 3.2GB total. During development I've been using a single ES node with default VM and ES settings on a box with 4GB of RAM. I've been happy with performance (most queries under 100ms) but haven't tested this setup under load. I'm preparing to start a phased roll out to production and need advice about what tweaks I should make. Production traffic should be relatively low.
> 
> Here is some more information:
> 
> cluster health: [cluster health · GitHub](https://gist.github.com/1676855)
> 
> cluster state: [cluster state · GitHub](https://gist.github.com/1676864)
> 
> cluster nodes: [cluster nodes · GitHub](https://gist.github.com/1676870)
> 
> status: [status · GitHub](https://gist.github.com/1676878)
> 
> What, if anything, should I do as a starting point to prepare for production use?
> 
> 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:** [July 6, 2017, 3:41am UTC](https://discuss.elastic.co/t/advice-for-production-configuration/6497/3 "2017-07-06T03:41:32Z")

</div>