Crowdsec has a consistently large virtual memory size (1.3GB shown) meaning it could easily fill a lot of memory if something goes wrong. Can this be reduced?
Since it is essentially parsing log files and sending messages, I don’t see why it should be so big.
On this server (1.3GB) there is no scenario, it is LAPI only. All of my containers with scenarios are even worse:
I wasn’t aware there was a backend database? It is a fairly default install, I haven’t added one. mysqld pictured is not related.
The firewall bouncer in the screenshot has an equally large virtual memory size.
This is actually normal because crowdsec (and the firewall bouncer) are written in go. Due to the way the go memory allocator works, a large amount of virtual memory can be allocated (see Frequently Asked Questions (FAQ) - The Go Programming Language).