Poor performance

[tanpro260196]

Load time for almost any sites increased by tenfold compared to the original NPM. Regardless of detect/prevent mode and level.

Sometime a site just timeout while initiating connection, especially if the site have a lot of images.

[orianelou]

Hi @tanpro260196,

We're looking into this, could you please share your system's specs (CPU, RAM)? you can also send us the details to [email protected].

Thank you! and hope to have some good news soon,

Oriane
open-appsec team

[tanpro260196]

Hi,

I am running it on an old PC.
CPU: i7 8700 (non-k)
16GB of ram DDR4.

[tanpro260196]

Hi there, is there any update?

[mgrimace]

Ok adding to this, appsec-agent is consistently running between 200-400% of my cpu according to docker stats
Proxmox, 10 cores, 32 gb ram, Debian 12 LXC, i7 8700

[mgrimace]

Follow-up: removing open-appsec and going back to stock NPM dropped my overall Proxmox server CPU use from 40ish% to 8%.

[jiriteach]

Yup - I have experienced this as well. Similar processor and have the agent on Docker running ~ 45-50% CPU even when its not doing much. Managed to setup everything as required and works well but the increased CPU is an issue.

[jiriteach]

So I've tried the Linux Embedded Agent for comparison and the CPU usage is only ~ 5-8%. Any reason why its so hard on the Docker container version? Anything that can be done to optimise? Might have to use the Linux Embedded Agent and normal NGINX as opposed to NPM.

[brandonkal]

Any update on this? Would it be possible to use NPM for nginx and appsec config generation but run nginx on the host?
I am experimenting with using Nomad to run the WAF tasks

[AnnoyingTechnology]

Any update on this ? @orianelou