beautypg.com

Measure performance of display changes, Measure performance of, Display changes – Rockwell Automation Migrating PanelView Enhanced Terminal Applications User Manual

Page 125: Age 125

background image

Publication 2711P-QS001A-EN-P - October 2007

125

Measure and Improve Runtime Application Performance Chapter 9

Measure Performance of
Display Changes

During performance benchmarking, you may want to measure the
time it takes for the application to change from one display to another.
It is important that the operator experiences the same display
feedback, if not better, on the PanelView Plus terminal.

If possible, place your PanelView ‘e’ terminal and the new PanelView
Plus terminal side by side. Run the original PanelView ‘e’ application
and the converted PanelView Plus application at the same time. You
should be able to notice any performance issues when changing
displays.

Follow these steps to measure the length of time it takes to change
from one display to another in the application.

1. Load and run your converted application on the PanelView Plus

terminal.

2. Use a stopwatch in the next steps to record the time it takes to

change from one display to another display.

3. At any display, press the Display Change button and start

recording the time.

4. Stop recording the time after all tag information is loaded on the

next display.

5. Repeat steps 3 and 4 until you have recorded the times for all

displays in the application.

6. If possible, repeat this procedure for the same application on the

PanelView ‘e’ terminal.

In a FactoryTalk View ME application, each display can have a
maximum of 1000 tag connections assigned. The more tag
connections a display has, the longer it will take to load the display.

If performance is slower for some displays in the PanelView Plus
application, you can:

adjust the maximum tag update rate for these displays.

reduce the number of tags used on these displays.

IMPORTANT

Cycle through all displays at least twice. The first
time you open a display it loads slower than
subsequent displays because tag information is
cached into memory after a display is opened.