Configuring how many events the poller reads

Large increases in the number of network events can slow down the polling process, ncp_poller. To minimize the performance impact of sudden increases in events, you can define how many network events the poller reads.

About this task

The polling process, ncp_poller, reads events from the NCMONITOR.activeEvent table into memory at intervals in order to determine the initial state of polling events. You can put an upper limit on the number of events that the poller reads. Additional events are not read into memory. When the number of events decreases below the limit again, the poller resumes reading events.

To configure a limit to the number of events that the poller reads, complete the following steps:

1. Back up and edit the following file: NcPollerSchema.cfg.
2. Edit, uncomment, or add the following line:

   update config.properties set EventThrottle = number_of_events

   where number_of_events is the maximum number of events that the poller will read. If this line is not present, there is no limit to the number of events that the poller attempts to process.

3. Save and close the file.