# Logstash 6.2.1 - windows memory issues **URL:** \ **Category:** Logstash\ **Created:** [March 26, 2018, 11:58am UTC](https://discuss.elastic.co/t/logstash-6-2-1-windows-memory-issues/125593 "2018-03-26T11:58:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![deepaks](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@deepaks](https://discuss.elastic.co/u/deepaks)\ **Post date:** [March 26, 2018, 11:58am UTC](https://discuss.elastic.co/t/logstash-6-2-1-windows-memory-issues/125593/1 "2018-03-26T11:58:02Z")
Hello I am having memory allocation and saturation issues with logstash. My logstash configuration has memory allocation of 20GB set in the jvm options(-Xms20g -Xmx20g) but after starting the service the total memory allocated is not 20GB but starts in the low 1 GB and steadily increases upto 20 GB over a period time. The pipeline processing is quick initially but once it reaches the maximum allocation 20GB the processing of logs slows down dramatically. I have to restart logstash and it picks pace again. I have persistent queue enabled. My questions is - When installing logstash in windows is it supposed to allocate the 20 GB once the service is started ? But in ES the allocation is done to the value specified in the jvm.options when the service starts. - Why does the log processing saturate after reaching the maximum allocation ? Not sure if the GC is kicking in or not. My configuration 3 logstash instances 8core CPU and 30 GB RAM pipeline.workers: 16 pipeline.output.workers: 8 pipeline.batch.size: 1000 Pipeline has 8 filebeat inputs and outputs which writes to multiple time based indexes around 40 based on the incoming data. 6 data nodes in ES. I don't see any errors in the ES nodes. Let me know if further details are required to answer my question. ---
**Author:** ![deepaks](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@deepaks](https://discuss.elastic.co/u/deepaks)\ **Post date:** [March 27, 2018, 8:44am UTC](https://discuss.elastic.co/t/logstash-6-2-1-windows-memory-issues/125593/2 "2018-03-27T08:44:36Z")
Using JvisualVM I managed to figure out what is happening in the heap and adjusted my pipeline settings accordingly. So far so good. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2018, 8:45am UTC](https://discuss.elastic.co/t/logstash-6-2-1-windows-memory-issues/125593/3 "2018-04-24T08:45:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.