NetXMS Support Forum

Hello

My current setup has grown litle bit and i have noticed errors stating "Syncer Thread not responding" they come and go. Am i hitting the server limit or is there some tuning to be done ?

It should be mostly default values. Where can i start investigating what is bottlenecking ?

Show syncer:
Last run at 15.Jun.2021 13:57:30
Last run time 6209ms
Average run time 9401ms
Max run time 125363ms
min run time 780ms

Show stats:
Objects 37665
Monitored nodes 5492
Collectible DCIs 15629
Active Alarms 260
Uptime 8days 5:03:59

Show dbstats:
Total 325370473
Select 70711371
Non-Select 254660971
Long running 0
Failed 0
Background writer requests
Dci data 81621137
Dci raw data 92416673
others 267627

Egert

Hi,

this could indicate bottleneck when objects are being saved to database. Try to enable parallel writes by increasing values of parameters ThreadPool.Syncer.BaseSize and ThreadPool.Syncer.MaxSize (I would recommend starting with 3 or 4 and see if there will be any difference). You may also increase value of SyncInterval to reduce number of writes. It also probably worth checking database performance.

Best regards,
Victor

I set ThreadPool.Syncer.BaseSize and ThreadPool.Syncer.MaxSize to 4 will let it run for a bit.

Any good metrics to monitor to indicate Netxms performance issues ?

There's out of the box template for server monitoring which has a number of DCIs for queue and thread wait time monitoring. If you were upgrading from previous version this may not have imported, unless ImportConfigurationOnStartup server configuration parameter is set to "Always".
You can just take this template file from server file system and import it via nxmc - it's here: share/netxms/templates/netxms_server.xml

Monitoring of database is also a good thing. If you use Postgres, there is subagent for it which provides a number of parameters that could be useful.

Indeed the template was missing, got it fixed. Database is MS Sql and data disk is 1tb ssd in raid 1, disk write,read and idle times are basicly non existing so drive is keeping up nicely.