# Tuning elasticsearch node client non-heap memory consumption

**URL:** <https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601>\
**Category:** Elasticsearch\
**Created:** [January 13, 2015, 10:37am UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601 "2015-01-13T10:37:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Itai\_Frenkel](https://avatars.discourse-cdn.com/v4/letter/i/ecc23a/32.png) [@Itai\_Frenkel](https://discuss.elastic.co/u/Itai_Frenkel)\
**Post date:** [January 13, 2015, 10:37am UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601/1 "2015-01-13T10:37:22Z")

</div>

Hello,

We are running a node client on each machine with small JVM heap -Xms384m  
-Xmx384m -Xss256k which is suitable for our use case.  
There are however another 285MB non-heap memory (676-389=285).  
How can this extra non-heap memory usage be configured ? What is it used  
for ?  
Below are the relevant node stats.

Regards,  
Itai

"process": {  
"open\_file\_descriptors": 340,  
"mem": {  
"resident\_in\_bytes": 676884480,  
"share\_in\_bytes": 23248896,  
"total\_virtual\_in\_bytes": 1696899072  
}  
},  
"jvm": {  
"mem": {  
"heap\_used\_in\_bytes": 44794784,  
"heap\_used\_percent": 11,  
"heap\_committed\_in\_bytes": 389283840,  
"heap\_max\_in\_bytes": 389283840,  
"non\_heap\_used\_in\_bytes": 44208640,  
"non\_heap\_committed\_in\_bytes": 44564480,  
"pools": {  
"young": {  
"used\_in\_bytes": 13765016,  
"max\_in\_bytes": 107479040,  
"peak\_used\_in\_bytes": 107479040,  
"peak\_max\_in\_bytes": 107479040  
},  
"survivor": {  
"used\_in\_bytes": 5086896,  
"max\_in\_bytes": 13369344,  
"peak\_used\_in\_bytes": 13369344,  
"peak\_max\_in\_bytes": 13369344  
},  
"old": {  
"used\_in\_bytes": 25942872,  
"max\_in\_bytes": 268435456,  
"peak\_used\_in\_bytes": 25942872,  
"peak\_max\_in\_bytes": 268435456  
}  
}  
},

--  
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/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\
**Post date:** [January 13, 2015, 10:56am UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601/2 "2015-01-13T10:56:19Z")

</div>

Why would you want that?

Locking heap memory usage is done by Elasticsearch on data nodes to reduce  
GC rounds, mainly because it loads a lot of data that is best managed by ES  
itself.

On client nodes you don't need that (and if you did, you wouldn't be using  
that small heap sizes)

--

Itamar Syn-Hershko  
[http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko)  
Freelance Developer & Consultant  
Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/)

On Tue, Jan 13, 2015 at 12:37 PM, Itai Frenkel [itaifrenkel@live.com](mailto:itaifrenkel@live.com) wrote:

> Hello,
> 
> We are running a node client on each machine with small JVM heap -Xms384m  
> -Xmx384m -Xss256k which is suitable for our use case.  
> There are however another 285MB non-heap memory (676-389=285).  
> How can this extra non-heap memory usage be configured ? What is it used  
> for ?  
> Below are the relevant node stats.
> 
> Regards,  
> Itai
> 
> "process": {  
> "open\_file\_descriptors": 340,  
> "mem": {  
> "resident\_in\_bytes": 676884480,  
> "share\_in\_bytes": 23248896,  
> "total\_virtual\_in\_bytes": 1696899072  
> }  
> },  
> "jvm": {  
> "mem": {  
> "heap\_used\_in\_bytes": 44794784,  
> "heap\_used\_percent": 11,  
> "heap\_committed\_in\_bytes": 389283840,  
> "heap\_max\_in\_bytes": 389283840,  
> "non\_heap\_used\_in\_bytes": 44208640,  
> "non\_heap\_committed\_in\_bytes": 44564480,  
> "pools": {  
> "young": {  
> "used\_in\_bytes": 13765016,  
> "max\_in\_bytes": 107479040,  
> "peak\_used\_in\_bytes": 107479040,  
> "peak\_max\_in\_bytes": 107479040  
> },  
> "survivor": {  
> "used\_in\_bytes": 5086896,  
> "max\_in\_bytes": 13369344,  
> "peak\_used\_in\_bytes": 13369344,  
> "peak\_max\_in\_bytes": 13369344  
> },  
> "old": {  
> "used\_in\_bytes": 25942872,  
> "max\_in\_bytes": 268435456,  
> "peak\_used\_in\_bytes": 25942872,  
> "peak\_max\_in\_bytes": 268435456  
> }  
> }  
> },
> 
> --  
> 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/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAHTr4ZuWvT7Co6PMJZjYY5tA1XTtiMaBHRZDyynX4zKTmC%3D6Bg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuWvT7Co6PMJZjYY5tA1XTtiMaBHRZDyynX4zKTmC%3D6Bg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Itai\_Frenkel](https://avatars.discourse-cdn.com/v4/letter/i/ecc23a/32.png) [@Itai\_Frenkel](https://discuss.elastic.co/u/Itai_Frenkel)\
**Post date:** [January 13, 2015, 9:14pm UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601/3 "2015-01-13T21:14:05Z")

</div>

I would like to reduce the amount of non-heap memory used by a client node.  
I would like to reclaim as much as I can from these 280MB, what is it used  
for?

On Tuesday, January 13, 2015 at 12:56:32 PM UTC+2, Itamar Syn-Hershko wrote:

> Why would you want that?
> 
> Locking heap memory usage is done by Elasticsearch on data nodes to reduce  
> GC rounds, mainly because it loads a lot of data that is best managed by ES  
> itself.
> 
> On client nodes you don't need that (and if you did, you wouldn't be using  
> that small heap sizes)
> 
> --
> 
> Itamar Syn-Hershko  
> [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko)  
> Freelance Developer & Consultant  
> Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/)
> 
> On Tue, Jan 13, 2015 at 12:37 PM, Itai Frenkel \<[itaif...@live.com](mailto:itaif...@live.com)  
> \<javascript:\>\> wrote:
> 
> > Hello,
> > 
> > We are running a node client on each machine with small JVM heap -Xms384m  
> > -Xmx384m -Xss256k which is suitable for our use case.  
> > There are however another 285MB non-heap memory (676-389=285).  
> > How can this extra non-heap memory usage be configured ? What is it used  
> > for ?  
> > Below are the relevant node stats.
> > 
> > Regards,  
> > Itai
> > 
> > "process": {  
> > "open\_file\_descriptors": 340,  
> > "mem": {  
> > "resident\_in\_bytes": 676884480,  
> > "share\_in\_bytes": 23248896,  
> > "total\_virtual\_in\_bytes": 1696899072  
> > }  
> > },  
> > "jvm": {  
> > "mem": {  
> > "heap\_used\_in\_bytes": 44794784,  
> > "heap\_used\_percent": 11,  
> > "heap\_committed\_in\_bytes": 389283840,  
> > "heap\_max\_in\_bytes": 389283840,  
> > "non\_heap\_used\_in\_bytes": 44208640,  
> > "non\_heap\_committed\_in\_bytes": 44564480,  
> > "pools": {  
> > "young": {  
> > "used\_in\_bytes": 13765016,  
> > "max\_in\_bytes": 107479040,  
> > "peak\_used\_in\_bytes": 107479040,  
> > "peak\_max\_in\_bytes": 107479040  
> > },  
> > "survivor": {  
> > "used\_in\_bytes": 5086896,  
> > "max\_in\_bytes": 13369344,  
> > "peak\_used\_in\_bytes": 13369344,  
> > "peak\_max\_in\_bytes": 13369344  
> > },  
> > "old": {  
> > "used\_in\_bytes": 25942872,  
> > "max\_in\_bytes": 268435456,  
> > "peak\_used\_in\_bytes": 25942872,  
> > "peak\_max\_in\_bytes": 268435456  
> > }  
> > }  
> > },
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [January 13, 2015, 10:10pm UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601/4 "2015-01-13T22:10:33Z")

</div>

I'd guess that'd be virtual memory, that the OS handles.

On 14 January 2015 at 10:14, Itai Frenkel [itaifrenkel@live.com](mailto:itaifrenkel@live.com) wrote:

> I would like to reduce the amount of non-heap memory used by a client  
> node. I would like to reclaim as much as I can from these 280MB, what is it  
> used for?
> 
> On Tuesday, January 13, 2015 at 12:56:32 PM UTC+2, Itamar Syn-Hershko  
> wrote:
> 
> > Why would you want that?
> > 
> > Locking heap memory usage is done by Elasticsearch on data nodes to  
> > reduce GC rounds, mainly because it loads a lot of data that is best  
> > managed by ES itself.
> > 
> > On client nodes you don't need that (and if you did, you wouldn't be  
> > using that small heap sizes)
> > 
> > --
> > 
> > Itamar Syn-Hershko  
> > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko)  
> > Freelance Developer & Consultant  
> > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/)
> > 
> > On Tue, Jan 13, 2015 at 12:37 PM, Itai Frenkel [itaif...@live.com](mailto:itaif...@live.com) wrote:
> > 
> > > Hello,
> > > 
> > > We are running a node client on each machine with small JVM  
> > > heap -Xms384m -Xmx384m -Xss256k which is suitable for our use case.  
> > > There are however another 285MB non-heap memory (676-389=285).  
> > > How can this extra non-heap memory usage be configured ? What is it used  
> > > for ?  
> > > Below are the relevant node stats.
> > > 
> > > Regards,  
> > > Itai
> > > 
> > > "process": {  
> > > "open\_file\_descriptors": 340,  
> > > "mem": {  
> > > "resident\_in\_bytes": 676884480,  
> > > "share\_in\_bytes": 23248896,  
> > > "total\_virtual\_in\_bytes": 1696899072  
> > > }  
> > > },  
> > > "jvm": {  
> > > "mem": {  
> > > "heap\_used\_in\_bytes": 44794784,  
> > > "heap\_used\_percent": 11,  
> > > "heap\_committed\_in\_bytes": 389283840,  
> > > "heap\_max\_in\_bytes": 389283840,  
> > > "non\_heap\_used\_in\_bytes": 44208640,  
> > > "non\_heap\_committed\_in\_bytes": 44564480,  
> > > "pools": {  
> > > "young": {  
> > > "used\_in\_bytes": 13765016,  
> > > "max\_in\_bytes": 107479040,  
> > > "peak\_used\_in\_bytes": 107479040,  
> > > "peak\_max\_in\_bytes": 107479040  
> > > },  
> > > "survivor": {  
> > > "used\_in\_bytes": 5086896,  
> > > "max\_in\_bytes": 13369344,  
> > > "peak\_used\_in\_bytes": 13369344,  
> > > "peak\_max\_in\_bytes": 13369344  
> > > },  
> > > "old": {  
> > > "used\_in\_bytes": 25942872,  
> > > "max\_in\_bytes": 268435456,  
> > > "peak\_used\_in\_bytes": 25942872,  
> > > "peak\_max\_in\_bytes": 268435456  
> > > }  
> > > }  
> > > },
> > > 
> > > --  
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%  
> > > [40googlegroups.com](http://40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/178f4f2f-5dfe-418e-82a3-de505a9ebd9a%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > 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/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/1d287a86-a84d-4e0f-b914-c7013b4d6ce1%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEYi1X\_J%2Bm9D7pK4dZTs2\_fLFOC4rC3Qw9%3D8s\_6eY3tahAcdBg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_J%2Bm9D7pK4dZTs2_fLFOC4rC3Qw9%3D8s_6eY3tahAcdBg%40mail.gmail.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, 12:39am UTC](https://discuss.elastic.co/t/tuning-elasticsearch-node-client-non-heap-memory-consumption/21601/5 "2017-07-06T00:39:14Z")

</div>


