3 ms·
Maybe I'm old-fashioned, but I find even 4MB complete overkill for the required functionality. All the damn thing needs to do is keep a couple of running count
by barrkel 14y ago
Maybe I'm old-fashioned, but I find even 4MB complete overkill for the required functionality.
All the damn thing needs to do is keep a couple of running counters on a short buffer of IPs and run iptables when limits are met, and a periodic parse of a log file. This feels like something where 64k ought to be enough for anyone, much less 640k!
Sure, we can get by with a fifth of a gigabyte of swap space for this task. Ugh. I've spent too much of my life in debugger CPU views. Jack's quivering tower of abstractions writhes in repulsion.
- ars 14y agoIt's written in python, which takes about about 2m-5m just to get out of bed with nothing loaded or running. (I don't consider that a lot BTW, not a ding on python.) There's about 200K of source code, but basically all the overhead is the python runtime. (The memory usage of python doing nothing varied on different machines, but was always virtually identical to the usage of fail2ban.) Also, the virt usage is mostly large memory mapped logfiles, not actual swap usage.