Adjust the Configuration of any Points that Cause a High Load
A high load on the ClearSCADA server can cause slow system performance (see Diagnose Client Performance Problems in the ClearSCADA Guide to the Server Status Tool). By using the statistics that are shown in Lists and Status displays, you may be able to identify any Kingfisher outstations (and points) that are causing a high load on the server. High load is often caused by a point updating at too frequently.
Where a point on a Kingfisher outstation is causing a high load:
- If the point is on an outstation that has a direct connection to the server, check the Scan Group that the point is using (see Configure Common Point Properties). If this is causing the server to update the current point value at too frequent a rate, you might need to:
- Specify a different Scan Group.
or:
- Specify a less frequent scan rate for the Scan Group (see Define Intervals for Timed Current Data Updates in the ClearSCADA Guide to Advanced Drivers).
- Specify a different Scan Group.
- If historic data is being logged for a point, you might need to decrease the frequency with which that data is logged (see Log Point Data on Kingfisher Outstations).
- If the point is an analog or counter point, enable the Significant Change feature. For analog points, see Define the Criteria for a Significant Change in Value in the ClearSCADA Guide to Core Point Configuration; for counter points, see Significant Change Properties.
- If the point is an analog point, or counter point with Significant Change enabled, you might need to increase the Significant Change deadband. This deadband defines the amount by which the point value has to change before the value will be logged by the outstation. For analog points, see Define the Criteria for a Significant Change in Value in the ClearSCADA Guide to Core Point Configuration; for counter points, see Significant Change Properties.
- If fleeting changes in value are causing a high load, you might want to increase the Persistence settings for the point (see Use Persistence to Stop Fleeting Changes in Value from Changing a Point State). However, a sudden increase in momentary changes in state might indicate a problem elsewhere. For this reason, you should examine the outstation, plant, and instrumentation for any underlying hardware problem that may be causing the sudden increase.
- If none of the above checks and configuration changes have cleared the high load caused by the point, check the following equipment for any faults:
- Outstation hardware
- Plant
- Instrumentation.