For best performance, CPU intensive processes like :ref:`zeek` and :ref:`suricata` should be pinned to specific CPUs. In most cases, you'll want to pin sniffing processes to the same CPU that your sniffing NIC is bound to. For more information, please see the Performance subsection in the appropriate :ref:`suricata` and :ref:`zeek` sections.
hdparm to gather drive statistics and alter settings, as described here:vm.dirty_ratio is the maximum amount of system memory that can be filled with dirty pages before everything must get committed to disk.
vm.dirty_background_ratio is the percentage of system memory that can be filled with “dirty” pages, or memory pages that still need to be written to disk -- before the pdflush/flush/kdmflush background processes kick in to write it to disk.
You will want to make sure that each part of the pipeline is operating at maximum efficiency. Depending on your configuration, this may include :ref:`elastic-agent`, :ref:`logstash`, :ref:`redis`, and :ref:`elasticsearch`.