# Elasticsearch 5.0.1 virtual memory overflow **URL:** \ **Category:** Elasticsearch\ **Created:** [December 11, 2017, 7:20am UTC](https://discuss.elastic.co/t/elasticsearch-5-0-1-virtual-memory-overflow/111023 "2017-12-11T07:20:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Prateek\_Gupta](https://avatars.discourse-cdn.com/v4/letter/p/f17d59/32.png) [@Prateek\_Gupta](https://discuss.elastic.co/u/Prateek_Gupta)\ **Post date:** [December 11, 2017, 7:20am UTC](https://discuss.elastic.co/t/elasticsearch-5-0-1-virtual-memory-overflow/111023/1 "2017-12-11T07:20:21Z")
I am using ElasticSearch 5.0.1 with Xmx and Xms as 8GB on a Linux machine. The main memory usage is under control but the virtual memory usage is around 420GB for ElasticSearch process. Custom properties set under elasticsearch.yml are bootstrap.memory\_lock: true and bootstrap.seccomp: false. Can this high usage of virtual memory impact the query and index performance of ElasticSearch? If yes, then how can I reduce the size and usage of virtual memory? ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [December 12, 2017, 5:36pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-1-virtual-memory-overflow/111023/2 "2017-12-12T17:36:05Z")
Using a lot of virtual memory is fine. See [http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html](http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 9, 2018, 5:36pm UTC](https://discuss.elastic.co/t/elasticsearch-5-0-1-virtual-memory-overflow/111023/3 "2018-01-09T17:36:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.