Performance Tuning Guide - EMC Community Network
Performance Tuning Guide - EMC Community Network
Performance Tuning Guide - EMC Community Network
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Designing the Application<br />
Note: Composite indexes cannot be created across different types (simple process variables) or across<br />
single value and repeating value attributes in the same type.<br />
Note: Have a database administrator determine which columns of a table to index. Creating too<br />
many indexes can cause update and insert statements to perform poorly.<br />
See <strong>EMC</strong> Documentum Content Server DQL Reference Manual and <strong>EMC</strong> Documentum Content Server<br />
Fundamentals for information on using make_index to create a composite index.<br />
Minimizing fetch operations<br />
During operations like opening a task, xCP extracts process variable attribute values and displays<br />
the data on a form. For each process variable whose attribute displays on a form, xCP performs a<br />
fetch operation for the process variable and its parent object. Design forms that require the fewest<br />
number of fetch operations (involve the fewest number of process variables) as each fetch operation<br />
affects performance.<br />
For example, when using simple process variables only, a form with 50 fields performs 100 discrete<br />
fetches. When using a single SDT to provide the 50 fields of information, the form performs only 2<br />
discrete fetches, which results in far better performance.<br />
Note: Forms that perform fewer than 60 fetches open in 2-3 seconds. Reducing the number of fetches<br />
to less than 60 does not result in significant performance improvement.<br />
Note: Content Server 6.6 provides for caching of the parent object after initial fetching. As a result,<br />
the number of fetches (after the initial fetch) reduces by half (1 per process variable rather than 2<br />
per process variable).<br />
Note: Making a process variable invisible does not prevent an object fetch but it does result in a slight<br />
performance improvement (Hiding unused variables, page 39).<br />
Analyzing process variable usage (measuring fetches), page 75 provides information on measuring<br />
the number of object fetches in your application.<br />
Hiding unused variables<br />
Process Builder provides the option to mark process variables as visible for manual activities. Making<br />
a process variable invisible improves performance by reducing processing overhead associated<br />
with the form. If no form fields use a process variable, hide the process variable by deselecting the<br />
checkbox in the process variable definition (Figure 13, page 40).<br />
<strong>EMC</strong> Documentum xCP 1.0 <strong>Performance</strong> <strong>Tuning</strong> <strong>Guide</strong> 39