# JVM settings for Logstash container **URL:** \ **Category:** Logstash\ **Tags:** docker\ **Created:** [May 22, 2020, 2:56am UTC](https://discuss.elastic.co/t/jvm-settings-for-logstash-container/233838 "2020-05-22T02:56:37Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![worapojc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/worapojc/32/42782_2.png) [@worapojc](https://discuss.elastic.co/u/worapojc)\ **Post date:** [May 22, 2020, 2:56am UTC](https://discuss.elastic.co/t/jvm-settings-for-logstash-container/233838/1 "2020-05-22T02:56:38Z")
Hi Elastic team, Currently, I'm using many Logstash instances to parse the customer logs. There are around 8 instances / server with 4GB JVM settings (-Xmx 4GB -Xms 4GB). The server have CPU 16 and Memory for 64GB. In this situation, I found these issues. - If a filter broke, it will broke for all customers. - If a filter/grok need to update, it will impacts to all customers (restart) - The flooding logs always take priority. I would like to enhance the pipeline by customer separation. From customer1..N --\> Logstash --\> ES To customer1 --\> Logstash\_cust1 --\> ES customer2 --\> Logstash\_cust2 --\> ES ... customerN --\> Logstash\_custN --\> ES I think the Logstash docker can solve this issue. However, do you have the best practice or guide lines for container configuration? - JVM for each container or should I limit the amount of the memory at the docker? - The number of Logstash worker per container. In case the physcial have CPU 16 RAM 64GB, and we have 100 customers. Should I set only 1 worker for container? Thank you, Worapoj ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 19, 2020, 2:56am UTC](https://discuss.elastic.co/t/jvm-settings-for-logstash-container/233838/2 "2020-06-19T02:56:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.