mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 06:37:19 -04:00
parent
dbcce19888
commit
b6ebbb3eed
2 changed files with 2 additions and 1 deletions
|
@ -3,7 +3,7 @@
|
|||
# Xms represents the initial size of total heap space
|
||||
# Xmx represents the maximum size of total heap space
|
||||
|
||||
-Xms256m
|
||||
-Xms1g
|
||||
-Xmx1g
|
||||
|
||||
################################################################
|
||||
|
|
1
docs/static/performance-checklist.asciidoc
vendored
1
docs/static/performance-checklist.asciidoc
vendored
|
@ -43,6 +43,7 @@ You may be tempted to jump ahead and change settings like `pipeline.workers` (`-
|
|||
* Often times CPU utilization can go through the roof if the heap size is too low, resulting in the JVM constantly garbage collecting.
|
||||
* A quick way to check for this issue is to double the heap size and see if performance improves. Do not increase the heap size past the amount of physical memory. Leave at least 1GB free for the OS and other processes.
|
||||
* You can make more accurate measurements of the JVM heap by using either the `jmap` command line utility distributed with Java or by using VisualVM. For more info, see <<profiling-the-heap>>.
|
||||
* Always make sure to set the minimum (Xms) and maximum (Xmx) heap allocation size to the same value to prevent the heap from resizing at runtime, which is a very costly process.
|
||||
|
||||
. *Tune Logstash worker settings:*
|
||||
+
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue