# ElasticSearch Server Not Utilizing Full Memory

**URL:** <https://discuss.elastic.co/t/elasticsearch-server-not-utilizing-full-memory/17880>\
**Category:** Elasticsearch\
**Created:** [June 3, 2014, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-server-not-utilizing-full-memory/17880 "2014-06-03T09:58:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ajay\_Singh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ajay_singh/32/1516_2.png) [@Ajay\_Singh](https://discuss.elastic.co/u/Ajay_Singh)\
**Post date:** [June 3, 2014, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-server-not-utilizing-full-memory/17880/1 "2014-06-03T09:58:08Z")

</div>

I have recently deployed ElasticSearch at our local servers as well as on a  
client server.

As we know ElasticSearch uses 1GB memory (RAM) by default.

I increased this memory by setting the environment variable ES\_HEAP\_SIZE to  
4g on local server (where RAM is 8GB). On local server it immediately takes  
the given memory and starts using it.

However when we follow the same step on Client Server and set ES\_HEAP\_SIZE  
to 12g (RAM is 24GB), ElasticSearch seems to be using only 1GB at beginning  
which slowly increases. As a result on client servers we are getting very  
poor performance and even many service hits get timeout.

We have verified that JVM is actually getting the allocated memory size,  
but somehow this memory is not being utilized by ElasticSearch on Client  
servers.

Our local server is Windows 7 Professional SP1, while client server has got  
Windows 2012 R2 Standard edition.

Please help me with this issue. I have 64bit version of jdk1.7.0\_55 on  
Windows 2012 R2.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d29181a7-74a8-4f20-83bd-b0e858b92e92%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d29181a7-74a8-4f20-83bd-b0e858b92e92%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:25am UTC](https://discuss.elastic.co/t/elasticsearch-server-not-utilizing-full-memory/17880/2 "2017-07-06T01:25:00Z")

</div>