...
- Scaling NMIS Polling
- Scaling NMIS polling - how NMIS handles long running processes
- NMIS 8 - Configuration Options for Server Performance Tuning
- NMIS 9 - Configuration Options for Server Performance Tuning
- opCharts 3 Performance Tuning
...
Opmantek Applications
This article configurations are related to Opmantek products. opCharts, opEvents, opConfig, opHA, opReports, ... all use the omkd daemon which servers the frontend requests. Also, opEvents, opCharts and opConfig have their own daemons.
...
The performance logs are really useful for debugging purposes, but they also can affect performance. So, it is recommended to turn them off when they are not necessary:
| Code Block |
|---|
omkd_performance_logs => false |
...
Two servers are compared in this section.
- Master Primary only have one node, but more than 400 poller nodes. opHA process is what will require more CPU and memory usage.
- Poller have more more than 500 nodes. nmis process will require more CPU and memory, for polling the information for all the nodes.
...
This is how the server memory graphs looks in a stressed system - We will be focused focus on the memory as it this is where the bottleneck is:
NMIS process keeps remains stable, is not using more than 120 mb, and the process was stopped - probably killed for the system due to high memory usage:
| Status | ||||
|---|---|---|---|---|
|
...
Daemons graphs:
omk:
mongo:
Stressed system
| Status | ||||||
|---|---|---|---|---|---|---|
|
System information:
| Name | Value |
|---|---|
| nmisd_max_workers | 50 |
| nmisd_scheduler_cycle | 30 |
| nmisd_worker_cycle | 10 |
| nmisd_worker_max_cycles | 10 |
nmis9d is crashing with no error messages.
Some server info:
- CentOS 7
- 463 Nodes
- Poller server
- High IO Wait
- increased open files to 100’000