Very slow when terminate/solve alarms

Started by hitzi, March 20, 2019, 02:31:52 PM

Previous topic - Next topic

hitzi

Hi,

when I terminate/solve for example 10 alarms at once it could last up to 3-4 minutes until the alarms are really terminated - I even get a timeout on the webui. The process netxmsd.exe consumes 25-30% CPU in all this time. Why does this happen and why is it so slow?

NetXMS runs on a Windows 2012 R2 Server with a MSSQL Express database.
show stats:
Objects: 1897
Monitored nodes: 301
Collectible DCIs: 3936
Active alarms: 34931

There are not that many nodes but the database size is 7GB. Why is this db so big and could this the problem which slows down terminating/solving alarms? I already shrinked/compress the db- this reduced the size from 8,5GB to 7GB.

show pollers: results most of the time is one object from type stat. From time to time there are more pollers.

The screenshot is from the time when I terminated 10 alarms at once.

Victor Kirhenshtein

Hi,

this is most likely related to relatively large total number of active alarms. We will investigate this further.

Best regards,
Victor


Victor Kirhenshtein

Update: we have found bug in alarm termination code, in upcoming release 2.2.14 this issue will be fixed.

Best regards,
Victor