# Memory usage seems excessive

**URL:** <https://discuss.elastic.co/t/memory-usage-seems-excessive/8014>\
**Category:** Elasticsearch\
**Created:** [June 8, 2012, 3:02am UTC](https://discuss.elastic.co/t/memory-usage-seems-excessive/8014 "2012-06-08T03:02:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![George\_Kappel](https://avatars.discourse-cdn.com/v4/letter/g/b77776/32.png) [@George\_Kappel](https://discuss.elastic.co/u/George_Kappel)\
**Post date:** [June 8, 2012, 3:02am UTC](https://discuss.elastic.co/t/memory-usage-seems-excessive/8014/1 "2012-06-08T03:02:26Z")

</div>

Using ES 19.3 and ES\_HEAP\_SIZE=1g

Node stats are here [https://gist.github.com/2893236](https://gist.github.com/2893236)  
Info is here [https://gist.github.com/2893271](https://gist.github.com/2893271)

The longer this runs the more memory gets used, currently 2.5g.  
Utilization of elasticsearch is very low, just 1 shard and a handful of  
documents and searches

What are the recommended steps to determine if this is a real problem? and  
if so is there anything that can be done to minimize memory use?

---

<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:** [June 10, 2012, 9:45pm UTC](https://discuss.elastic.co/t/memory-usage-seems-excessive/8014/2 "2012-06-10T21:45:34Z")

</div>

It does not use memory at all on the JVM level (you can see the heap\_used  
part there). Do you have any special configuration or index level  
configuration?

On Fri, Jun 8, 2012 at 5:02 AM, George Kappel [george.kappel@gmail.com](mailto:george.kappel@gmail.com)wrote:

> Using ES 19.3 and ES\_HEAP\_SIZE=1g
> 
> Node stats are here [elasticsearch node stats · GitHub](https://gist.github.com/2893236)  
> Info is here [elastic search node info · GitHub](https://gist.github.com/2893271)
> 
> The longer this runs the more memory gets used, currently 2.5g.  
> Utilization of elasticsearch is very low, just 1 shard and a handful of  
> documents and searches
> 
> What are the recommended steps to determine if this is a real problem? and  
> if so is there anything that can be done to minimize memory use?

---

<div class="post-metadata">

**Author:** ![George\_Kappel](https://avatars.discourse-cdn.com/v4/letter/g/b77776/32.png) [@George\_Kappel](https://discuss.elastic.co/u/George_Kappel)\
**Post date:** [June 11, 2012, 12:51pm UTC](https://discuss.elastic.co/t/memory-usage-seems-excessive/8014/3 "2012-06-11T12:51:13Z")

</div>

Yes heap used appears low but "ps aux" report 2gb resident and 4gb virtual  
for elasticsearch

No special configuration, on IRC it was recommended that I try a different  
JVM. Currently using openjdk will be trying oracle 7

On Sun, Jun 10, 2012 at 4:45 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> It does not use memory at all on the JVM level (you can see the heap\_used  
> part there). Do you have any special configuration or index level  
> configuration?
> 
> On Fri, Jun 8, 2012 at 5:02 AM, George Kappel [george.kappel@gmail.com](mailto:george.kappel@gmail.com)wrote:
> 
> > Using ES 19.3 and ES\_HEAP\_SIZE=1g
> > 
> > Node stats are here [elasticsearch node stats · GitHub](https://gist.github.com/2893236)  
> > Info is here [elastic search node info · GitHub](https://gist.github.com/2893271)
> > 
> > The longer this runs the more memory gets used, currently 2.5g.  
> > Utilization of elasticsearch is very low, just 1 shard and a handful of  
> > documents and searches
> > 
> > What are the recommended steps to determine if this is a real problem?  
> > and if so is there anything that can be done to minimize memory use?

---

<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:24am UTC](https://discuss.elastic.co/t/memory-usage-seems-excessive/8014/4 "2017-07-06T03:24:54Z")

</div>


