If performance degradation occurs in ASU mode

Minimize the number of rows in each view through the use of filters.

Every nn seconds (the number of seconds specified on the ASU command), MainView collects, sorts, filters, and calculates values for every row in every view. If fewer rows are present, less work is required of MainView.

For example, rather than updating the entire DEVSTAT view, use the CUSTom command to enter the view customization facility and establish a filter so that only the rows containing relevant information are visible-for example:

ServiceTime > 10

Specify a value of 15 seconds or more on the ASU command.

If you give MainView more time to perform the same amount of work, the strain on performance is naturally reduced.

Real-time views should not enter ASU mode with a value of less than 15 seconds, because real-time data is generally not updated more often than every 15 seconds.

Make sure that there are no unlocked views containing views that you do not want anyone to update: the VIEWS view, SCREENS view, or any view in historical mode.

ASU updates only unlocked windows. When MainView tries to update windows that are ineligible for updating, performance is degraded unnecessarily.