Designing processes - EMC Community Network
Designing processes - EMC Community Network
Designing processes - EMC Community Network
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Performance and Scalability<br />
Factors that affect performance and scalability<br />
This section describes the following factors that can affect performance and scalability:<br />
• Automatic activities, page 98<br />
• Search forms, page 98<br />
• Task lists, page 99<br />
• Preconditions, page 99<br />
• Skill-set matching, page 100<br />
• Logins, page 100<br />
Automatic activities<br />
To improve the performance of automatic activities in your process, make one user (or a small set<br />
of users) the performer of all the automatic activities. For example, if you define a user, such as<br />
auto_executor, and make that user the performer of all the automatic activities, the runtime execution<br />
of these automatic activities increases considerably.<br />
For security reasons, only a superuser can select a specific user as a performer for an automatic<br />
activity in Process Builder.<br />
Search forms<br />
A client may ask you to implement a more complex search option in TaskSpace. Even though it can<br />
be easy to configure multiple search options, advise the client against doing it. The difference in<br />
database performance (and maintenance) between three search options and four is enormous. The best<br />
performing applications enable users to complete their jobs with a minimum of actions and choices.<br />
<strong>Designing</strong> search forms that are seldom or never used is not advised.<br />
Minimize search criteria<br />
Design search forms with as few search criteria and columns as possible. This keeps application<br />
performance degradation to a minimum and makes any future scaling of the application easier. Each<br />
search criterion requires more maintenance by the database and adds load to the system. For instance,<br />
just one poorly constructed search form with many search options and columns can render the<br />
application non-operational. Before designing search forms, it is important that you fully understand<br />
the business use cases.<br />
Wildcard searches<br />
Avoid implementing wildcard searches because exact searches are the only searches that scale. All<br />
other types of searches involve some form of scanning (index or table), which can hinder the scalability<br />
of the database, and ultimately the entire application.<br />
It is important to separate what a client needs from what a client wants. The needs of the business<br />
should determine how search forms should be designed and used. System performance and future<br />
scalability become victim to over-engineered search forms. Articulate to the client the impact of search<br />
98 <strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide
Change language