# Elasticsearch overcommit (VSZ) 300-900% **URL:** \ **Category:** Elasticsearch\ **Created:** [December 15, 2019, 6:56pm UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919 "2019-12-15T18:56:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![111266](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111266/32/59400_2.png) [@111266](https://discuss.elastic.co/u/111266)\ **Post date:** [December 15, 2019, 6:56pm UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/1 "2019-12-15T18:56:29Z")
Hello. I dont know why i have very high VSZ (virtual memory size) ~ 800-900%, heap 4gb in settings ``` PID PPID CMD RSS VSZ %MEM %CPU 11554 1 /usr/bin/java -Xms4g -Xmx4g java 4974936 46637680 36.3 0.0 ``` I'm use LXD container with ubuntu 18.04 with limit to resources -- 13gb Ram and 4 core `Elasticsearch version 6.6.0` Configs JVM for Elastic cat /etc/elasticsearch/jvm.options ``` -Xms4g -Xmx4g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly --Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=${ES_TMPDIR} -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/lib/elasticsearch -XX:ErrorFile=/var/log/elasticsearch/hs_err_pid%p.log 8:-XX:+PrintGCDetails 8:-XX:+PrintGCDateStamps 8:-XX:+PrintTenuringDistribution 8:-XX:+PrintGCApplicationStoppedTime 8:-Xloggc:/var/log/elasticsearch/gc.log 8:-XX:+UseGCLogFileRotation 8:-XX:NumberOfGCLogFiles=32 8:-XX:GCLogFileSize=64m 9-:-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m 9-:-Djava.locale.providers=COMPAT 10-:-XX:UseAVX=2 ``` cat /proc/meminfo ``` MemTotal: 13671872 kB MemFree: 4857240 kB MemAvailable: 6115816 kB Buffers: 0 kB Cached: 1258576 kB SwapCached: 0 kB Active: 8171968 kB Inactive: 464476 kB Active(anon): 7367932 kB Inactive(anon): 124 kB Active(file): 804036 kB Inactive(file): 464352 kB Unevictable: 0 kB Mlocked: 33652304 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 2772 kB Writeback: 0 kB AnonPages: 73933548 kB Mapped: 3917012 kB Shmem: 9500 kB Slab: 0 kB SReclaimable: 0 kB SUnreclaim: 0 kB KernelStack: 125056 kB PageTables: 288648 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 157965700 kB Committed_AS: 122171068 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 512000 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 2520896 kB DirectMap2M: 109289472 kB DirectMap1G: 24117248 kB ``` cat /proc/sys/vm/overcommit\_ratio 120 cat /proc/sys/vm/overcommit\_memory 0 ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 16, 2019, 7:50am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/2 "2019-12-16T07:50:04Z")
That all looks fairly normal to me. What is your question? ---
**Author:** ![111266](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111266/32/59400_2.png) [@111266](https://discuss.elastic.co/u/111266)\ **Post date:** [December 16, 2019, 9:15am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/3 "2019-12-16T09:15:07Z")
why ES use 46637680 VSZ? in the HTOP --- 44.5G VIRT my heap size only 4Gb -Xms4g -Xmx4g ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 16, 2019, 10:02am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/4 "2019-12-16T10:02:12Z")
VSZ includes lots of things that aren't on the heap (or even in-memory) -- libraries, memory-mapped indices, and so on. It doesn't relate to the memory usage of the process, if that's what you are asking. ---
**Author:** ![111266](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111266/32/59400_2.png) [@111266](https://discuss.elastic.co/u/111266)\ **Post date:** [December 16, 2019, 10:12am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/5 "2019-12-16T10:12:37Z")
thank for answer can i reduce this VSZ size used by ES? ---
**Author:** ![Mikhail\_Khludnev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_khludnev/32/59591_2.png) [@Mikhail\_Khludnev](https://discuss.elastic.co/u/Mikhail_Khludnev)\ **Post date:** [December 16, 2019, 10:26am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/6 "2019-12-16T10:26:42Z")
Hello, 111266. I've earlier posted one advice [Is there a way to limit RES memory used by ES](https://discuss.elastic.co/t/is-there-a-way-to-limit-res-memory-used-by-es/209100/5) however I've found that it might be hard to get a point. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 16, 2019, 10:36am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/7 "2019-12-16T10:36:25Z")
> [@111266](#): > > can i reduce this VSZ size used by ES? Not really, but I'm not really understanding why you want to do this. Virtual memory isn't really a limited resource. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 13, 2020, 10:36am UTC](https://discuss.elastic.co/t/elasticsearch-overcommit-vsz-300-900/211919/8 "2020-01-13T10:36:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.