Performance Tuning Guide - EMC Community Network

Designing the Application
Figure 13. Hiding a process variable
Converting simple process variables to SDTs
If your design makes extensive use of simple process variables and you can use SDTs instead, create
new SDTs with attributes that map to the previously used simple process variables. Replace as many
process variables as possible with SDT attributes. Performance improves even if you consolidate the
simple process variables into several (instead of only one) SDTs. After creating the SDT, delete the
simple process variables for which the SDT provides an attribute.
If your application is already in production and you cannot consolidate simple process variables
into SDTs, hide those simple process variables that do not show up in any forms (Hiding unused
variables, page 39) If there are many process variables that are mandatory on the form because they
are mapped to a field and the application is in production and cannot be changed, create a workflow
template you can use while migrating off the old template.
Chapter 5, Designing Reports provides information on the potential performance impact of updating
the BAM database with an SDT definition.
Minimizing form size
Form size determines form rendering performance more than any other single factor. To maximize
form rendering performance, consider the following:
• Only use packages when necessary.
• Adaptor-based data increases form footprint and affects response time (Using adaptors, page 52).
• Use virtual documents or embedded folders, instead of tabs, to contain the forms or documents
needed for processing.
Form size impacts system sizing. A typical JVM can support anywhere between 40-200 users,
depending on the size of the forms involved in day to day business activities. The larger the forms,
the fewer users the JVM can support.
40 EMC Documentum xCP 1.0 Performance Tuning Guide