Refresh Performance

Diagrams User Guide

Diagrams : Getting Started : Optimising Project Performance and Storage Space : Refresh Performance

The performance of the Refresh command is dependent on how many shapes are being refreshed and how many attributes belong to each of these shapes in the Shape Data.

It is easy to get large numbers here. E.g. if there are a 100 shapes in a drawing that each has 50 attributes belonging to it, this will produce 5000 attribute values to be read from Dabacon and updated in the shapes' Shape Data.

Recommendations:

Only use the Refresh command when necessary, e.g. when you suspect something has been updated in the DB and you need to see it reflected in your drawing.

If only some shapes are selected in a drawing when doing the refresh, only those shapes will be affected. It is often unnecessary to refresh the whole drawing if only one part is being worked on.

Reduce the number of attributes per shape to be shown in Shape Data down to a set of attributes that are really being used by the Diagrams user. E.g. there exists a lot of .Pmg... UDA’s in the sample project. In many cases these attributes are not being used and take up unnecessary time during the Refresh. When these kinds of attributes are not being used the UDA’s can simply be removed from the project. It is also possible to control which attributes should appear in the Shape Data through the Attribute Presentation function. If for instance half of the attributes shown in the Shape Data are never used, then removing them will halve the time used for refreshing the whole drawing.