...
This is an example about how these parameters can impact in the performance of the server, in a server with 64 CPUs and more than 3700 nodes:
| When | abort_after | demote_faulty_nodes | CPU | Nodes No Collected | Other |
|---|---|---|---|---|---|
| Initial Configuration | Default (60 seg) | false | <50% (Aprox.) | 1100 ~ | totalPoll=3713 ontime=891 1x_late=1460 3x_late=41 12x_late=56 144x_late=1265 |
| 1 Test | 120 | true | <50% (Aprox.) | 500 ~ | N/A |
| 2 Test | 240 | true | <60% (Aprox.) | 240 ~ | totalPoll=1229 ontime=998 no_snmp=14 demoted=0 1x_late=217 3x_late=0 12x_late=0 144x_late=0 |
| 3 Test | 0 (Disabled) | true | Around 100% (Aprox.) | 0 | Took 7 minutes. Processed >3000 nodes. Disabled cron |
| 4 Test | 0 (Disabled) | true | 100% (Aprox.) | N/A | Commented while (wait for children) in nmis.pl |
| 5 Test | 0 (Disabled) | false | 100% (Aprox.) | N/A | N/A |
Note that problems in the modelling that throughs errors in the logs can also make the system slow. The polling time for each node will be increased, hence the polling cycle will take longer to run, and depending on the configuration options, the process can be aborted with nodes without being polled.
...