Skip to content
This repository was archived by the owner on Mar 17, 2025. It is now read-only.

Resource Usage

Jump to bottom
Jeremy Falling edited this page Jan 25, 2015 · 13 revisions

Memory and CPU usage

autoban can use a significant amount of memory on the host you run it on. The more traffic you have and the more data you configure autoban to look at, the more it will use. I under load tests I see between 10-90MB/process.

autoban can max out all of your cpus/cores. Some tasks fork, such as searching for data on ip addresses. The number of forks is configurable in autoban.conf and you will need to see what values work best for your use case. The more cores you can allocate to autoban, the faster it will be (up to a point).

To diagnose the resources usage, you can use time -l autoban.pl on OS X or time -v autoban.pl on linux (full path to time is usually required).

Elasticsearch Load

Lastly, depending on your ES cluster and how much data you are analyzing, this can put a high load on your ES cluster (or maybe crash it...).

The autoban project © Jeremy Falling. Published under the GNU General Public License version 3

Clone this wiki locally