30.01.2015 Views

Designing processes - EMC Community Network

Designing processes - EMC Community Network

Designing processes - EMC Community Network

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8<br />

Performance and Scalability<br />

This chapter discusses the following:<br />

• General approach to performance<br />

• System configuration guidelines<br />

• Factors that affect performance and scalability<br />

• Recommended application server settings<br />

• Recommended Content Server settings<br />

• Recommended database server settings<br />

• Tuning and troubleshooting performance problems<br />

General approach to performance<br />

This section discusses general performance theory. Performance analysis treats a large number of<br />

different metrics, such as response time, throughput, efficiency, and capacity. The two that are the most<br />

important to process-based applications are response time and throughput.<br />

• Response time measures the amount of time you must wait to receive any response to a request;<br />

for example, running a series of automated activities may incur a response time of one second<br />

between each one.<br />

• Throughput measures the number of transactions the system can process per unit of time; for<br />

example, a system may be able to handle only 100 TaskSpace searches per minute.<br />

As you design the application, you should:<br />

• Not go deep. The reason for the recommendation to not go deep is that every layer of database<br />

tables generates additional joins that impact performance. You should keep your inheritance<br />

hierarchy as flat as you can.<br />

• Tune for the highest-yield queries. Yield is the number of times a query is executed multiplied by<br />

the execution time of the query. By anticipating the yield and tuning it for the highest-yield query,<br />

your performance does not degrade unacceptably for that use case. To achieve this you may need to<br />

de-normalize, pulling attributes into one or two physical tables.<br />

In general, the recommended approach to performance testing is to carry out two classes of tests:<br />

• Single user profiling — In single-user profiling you run unit tests, such as collecting Documentum<br />

Class Library (DMCL)/DFC traces.<br />

• Load testing — In load testing you are looking for bottlenecks and capacity issues.<br />

<strong>EMC</strong> Documentum xCelerated Composition Platform Version 1.6 Best Practices Guide 95

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!