Performance Related Configuration Settings
The following table lists performance related engine configuration settings.
Limits the resources consumed by all NodeServices, not just those for Connect:Direct despite its name, by restricting the number that may communicate with their respective monitored servers simultaneously.
For optimum performance simultaneousCdPollers is typically set to 25% of the number of total number of polled monitored server types assigned to each EP with a maximum value of 30. This is just a guideline and not definitive however.
Specifies the limit on OSA records to be retrieved by the UnprocessedEventService from the CC_UNPROCESSED_EVENTtable.
This property is only used when OSA event processing is done synchronously.
A value in milliseconds that controls the frequency at which the EventProcessorService checks to see which OSA servers are late in sending in Heartbeat events, which is the indicator that they are down.
The larger this value is, the longer the delay could be for IBM® Sterling Control Center Monitor to ascertain that an OSA server has stopped communicating with IBM Sterling Control Center Monitor and that its status should change to Down.
Increasing this property value boosts performance and the expense of learning that OSA servers are down as soon as possible.
A value in milliseconds that controls the frequency at which the EventProcessorService checks for new OSA events to process from servers monitored by this EP.
Note when the number of OSA events processed matches eventsToProcessAtOnce no wait is performed between checks for new OSA events to process. This is referred to as catchup mode.
This property is only used when OSA event processing is done synchronously, which is controlled by the MULTI_THREAD_OSA_EVENT_PROCESSING property.