28.11.2014 Views

Performance Tuning Guide - EMC Community Network

Performance Tuning Guide - EMC Community Network

Performance Tuning Guide - 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.

Planning Capacity and Sizing<br />

Chapter 2<br />

This chapter provides the following capacity and sizing related sections:<br />

• Planning for peak or average loads, page 15<br />

• Planning for workflow database tables, page 17<br />

• Characterizing content, page 17<br />

• Capacity planning worksheet, page 18<br />

• Sizing the system, page 22<br />

The relationship between content (number of documents and average content size), flow (content<br />

ingested per time period), retention policies (content disposition rates), and growth projections affect<br />

your capacity planning. Plan your capacity to accommodate future content and flow. A small system<br />

comprised of a repository with 10 million objects and 2 million activities per day can grow to a large<br />

repository with 10 billion objects and 20 million activities per day.<br />

Plan your capacity to account for content disposition rates and auditability. Solutions that grow to<br />

1 million documents by ingesting 100,000 documents per year for ten years has a different impact<br />

from solutions that ingest and dispose of 1 million documents per day. Solutions that retain an audit<br />

trail for a long time have a significant impact, even if the daily workflow volume is small. After ten<br />

years, a solution which averages only 50 workflows per day can generate an audit trail database<br />

table with 100 million rows.<br />

Planning for peak or average loads<br />

Systems with high transaction volume or large usage (100,000 activities per hour, for example) can<br />

exhibit variable performance during certain time periods. Sizing the system for average rather than<br />

peak loads can result in degraded performance during peak load periods. For mission critical<br />

applications where downtime or performance degradation is unacceptable, size the system for peak<br />

loads.<br />

Gather all use case scenarios during the requirements phase. If there are periods when workloads<br />

spike (Figure 3, page 16), make sure to identify and use these volume metrics when sizing your<br />

system. When load testing, include single user, average-load, and peak-load scenarios.<br />

<strong>EMC</strong> Documentum xCP 1.0 <strong>Performance</strong> <strong>Tuning</strong> <strong>Guide</strong> 15

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

Saved successfully!

Ooh no, something went wrong!