improve efficiency of Suricata processing uploaded PCAP files #325
Labels
performance
Related to speed/performance
suricata
Relating to Malcolm's use of Suricata
upload
Relating to PCAP and/or Zeek log ingestion
Milestone
Currently as uploaded PCAP files are processed, each PCAP file results in a new suricata process for that PCAP file.
This is the same behavior for Zeek and Arkime capture; however, suricata seems to have more overhead (I often notice that suricata is still running on a batch of uploaded PCAP files long after the others are done).
I came across this thread describing using suricata socket control to send PCAP files to a single long-running suricata process, then output each eve.json to a different directory per-PCAP. This would be an improvement.
The text was updated successfully, but these errors were encountered: