Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update performance-checklist.asciidoc #16102

Open
wants to merge 1 commit into
base: 8.13
Choose a base branch
from
Open

Update performance-checklist.asciidoc #16102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/static/performance-checklist.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ sure-fire way to create a confusing situation.
* Memory
** Be aware of the fact that Logstash runs on the Java VM. This means that Logstash will always use the maximum amount of memory you allocate to it.
** Look for other applications that use large amounts of memory and may be causing Logstash to swap to disk. This can happen if the total memory used by applications exceeds physical memory.
** Consider disabling swap temporarily by running `sudo swapoff -a` or setting sysctl value of `vm.swappiness` is to `1`. You can turn off swapping permanently by commenting out every line that contains the word `swap` in `/etc/fstab` on Linux. The Windows equivalent is disabling the paging file under `System Properties → Advanced → Performance → Advanced → Virtual memory`.
* I/O Utilization
** Monitor disk I/O to check for disk saturation.
*** Disk saturation can happen if you’re using Logstash plugins (such as the file output) that may saturate your storage.
Expand Down
Loading