On Tue, 14 Aug 2012, r00t-Services.net Support wrote:
> I'm a little confused with fail2ban and it's multi threading support. In
> the wiki it says that multi threading is supported, but however, on all
> my setups it's only able to utilize 100% CPU (1 core).
I guess it is a dark side of the Python's GIL:
so even though there are multiple threads, they cannot use all CPUs at
the same time.
> Now with logs
> which are growing very fast (sometimes +2MB/s) the fail2ban-server
> process is far behind the most recent log entries. Is there any way to
> utilize every CPU core with fail2ban?
ad-hoc solution would be to start multiple fail2ban daemons monitoring
different jails... but not sure if that is worth the pain... we better
> Or would the new pyinotify backend
> might improve performance (haven't tried the new f2b version yet?
it might -- I would be really interested to hear the feedback if it +
newer version helps a bit
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419