# Elasticsearch 5.6 working set memory

**URL:** <https://discuss.elastic.co/t/elasticsearch-5-6-working-set-memory/148590>\
**Category:** Elasticsearch\
**Created:** [September 14, 2018, 9:16am UTC](https://discuss.elastic.co/t/elasticsearch-5-6-working-set-memory/148590 "2018-09-14T09:16:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rschirin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rschirin/32/45283_2.png) [@rschirin](https://discuss.elastic.co/u/rschirin)\
**Post date:** [September 14, 2018, 9:16am UTC](https://discuss.elastic.co/t/elasticsearch-5-6-working-set-memory/148590/1 "2018-09-14T09:16:38Z")

</div>

Hi all,  
I'm running an Elasticsearch cluster with just one node on a Windows Server 2012 R2.  
JVM configuration uses the default values with

```
-Xms 2g
-Xmx 2g

```

but when I checked the memory usage I saw that the `working set memory` value is up to 9gb.  
This could be really critical, so why seems that Elastic doesn't respect the configuration?

thanks in advance

---

<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:** [October 12, 2018, 9:16am UTC](https://discuss.elastic.co/t/elasticsearch-5-6-working-set-memory/148590/2 "2018-10-12T09:16:47Z")

</div>

Closed on October 12, 2018, 9:16am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.