-
-
Notifications
You must be signed in to change notification settings - Fork 372
Description
Is there an existing issue for this?
- I have searched the existing open and closed issues
Is your feature request related to a problem? Please describe
I have been using NetAlertX for a few years, on and off. I did notice that with time, the CPU usage has been going up steadily.
The image below indicates quite clearly when NetAlertX was started on the server. NetAlertX is basically using 6% of the whole system just for looking after itself. There are no plugins other than MQTT and ARP active, all other plugins have been disabled.
Using 6% to effectively just run a device presence check seems overly much. In comparison Zabbix server on a similar server, same CPU allocation, same hardware, runs at about 1% system use, collecting metrics from a dozen appliances and 4 servers, monitoring, checking for alerts and issuing notifications.
Zabbix Server:
Describe the solution you'd like
Looking at the amount of CPU cycles the program uses for effectively looking only after itself, it may be a good idea to consider a redesign of the internal workings. The CPU use will only increase with additional addons and features and may grow to an amount where it becomes not viable for operators to install it.
Describe alternatives you've considered
I keep testing NetAlertX on a semi regular basis as I like the UI and features.
However I have an instance of WatchYourLan running that uses less than 1% CPU of a single core compared to NetAlertX using 12% of 2 cores.
The MQTT and notification logic of WatchYourLan has been outsourced to Windmill that is running at 5% of 2 cores. Combined use of WatchYourLan and Windmill is 5.5% compared to NetAlertX with 12% of 2 cores, however Windmill is doing many other tasks with those CPU cycles.
It remains that NetAlertX is unacceptably high in its CPU use.
Anything else?
There are a few reports and it's not clear if that has ever been resolved.
#191 - no response from poster, closed
#203 - no confirmation if solved - closed
#230 - one confirmed, one not but clearly an unlaying bug somwhere
#769 - not clear if the issue was resolved or underlaying code was changed
Am I willing to test this? 🧪
- I will do my best to test this feature on the
netlertx-devimage when requested within 48h and report bugs to help deliver a great user experience for everyone and not to break existing installations.
Can I help implement this? 👩💻👨💻
- Yes
- No
