Hight CPU and MEM usage always #769
Description
Is there an existing issue for this?
- I have searched the existing open and closed issues and I checked the docs https://github.com/jokob-sk/NetAlertX/tree/main/docs
Current Behavior
Using lasted version in docker in Unraid
have a lot of cpu and mem for app at last time , db file has 1.7GB :
Expected Behavior
low usage
Steps To Reproduce
...
app.conf
# General
#---------------------------
LOADED_PLUGINS=['ARPSCAN','CSVBCKP','DBCLNP','DDNS','INTRNT','MAINT','NEWDEV','NSLOOKUP','NTFPRCS','PHOLUS','SETPWD','VNDRPDT','WEBHOOK','WORKFLOWS']
LOADED_PLUGINS__metadata="{}"
SCAN_SUBNETS=['192.168.0.0/24 --interface=bond0']
SCAN_SUBNETS__metadata="{}"
LOG_LEVEL='verbose'
LOG_LEVEL__metadata="{}"
TIMEZONE='Asia/Jerusalem'
TIMEZONE__metadata="{}"
PLUGINS_KEEP_HIST=10000
PLUGINS_KEEP_HIST__metadata="{}"
REPORT_DASHBOARD_URL='http://192.168.0.199:20211'
REPORT_DASHBOARD_URL__metadata="{}"
UI_LANG='English'
UI_LANG__metadata="{}"
UI_PRESENCE=['online','offline','archived']
UI_PRESENCE__metadata="{}"
UI_DEV_SECTIONS=[]
UI_DEV_SECTIONS__metadata="{}"
UI_MY_DEVICES=['online','offline','archived','new','down']
UI_MY_DEVICES__metadata="{}"
UI_NOT_RANDOM_MAC=[]
UI_NOT_RANDOM_MAC__metadata="{}"
UI_ICONS= [..redacted ...]
UI_ICONS__metadata="{}"
UI_REFRESH=0
UI_REFRESH__metadata="{}"
DAYS_TO_KEEP_EVENTS=90
DAYS_TO_KEEP_EVENTS__metadata="{}"
HRS_TO_KEEP_NEWDEV=0
HRS_TO_KEEP_NEWDEV__metadata="{}"
API_CUSTOM_SQL='SELECT * FROM Devices WHERE dev_PresentLastScan = 0'
API_CUSTOM_SQL__metadata="{}"
NETWORK_DEVICE_TYPES=['AP','Gateway','Firewall','Hypervisor','Powerline','Switch','WLAN','PLC','Router','USB LAN Adapter','USB WIFI Adapter','Internet']
NETWORK_DEVICE_TYPES__metadata="{}"
etc ...docker-compose.yml
...What branch are you running?
Production
app.log
...
Debug enabled
- I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.