Performance Tuning Guide - EMC Community Network

Designing Reports
Planning and testing
BAM reporting can be performance sensitive. To avoid performance issues, observe the following
guidelines during your planning:
• Plan for reporting at the beginning of the project.
• Conduct performance testing of your BAM reports in a test environment that simulates your
production environment regarding the following:
— a fully loaded BAM database
— anticipated volume of processes, activities, and audited business data
— high frequency report viewing
— multiple concurrent users.
Benchmark throughput and response time for your test environment under worst case scenarios.
• Size the BAM database to meet or exceed expected data throughput. Database requirements can
be sized using the BAM Dashboard Sizing Calculator spreadsheet, available in the BAM Database
Sizing Calculator folder of the bam-product-supplemental_files.zip file.
• Consider the size of the result set comprising the report. For reports with more than a few
hundred records, use Crystal Reports.
• Only audit and monitor process variables and packages that are reported on.
• Consider the number of entities queried when generating the report. If your result set is a few
hundred records, use more entities (up to 20). If your result set is thousand of records, limit the
number of entities to no more than five. The more columns selected, the fewer report entities used.
Reporting on intra-activity events
Content Server does not write activity data to the audit trail database table until an activity completes,
which can delay reporting on events happening within an activity, especially when your process
design consolidates multiple actions in the context of a single activity. To report on intra-activity
processes, divide the activity into multiple, more granular, activities in your process design.
Note: Creating more activities can have an adverse performance impact on workflow throughput
(Minimizing and consolidating activities, page 27).
Synchronizing the BAM database
BAM generates reports from BAM database tables. When the BAM database tables do not regularly
synchronize with the audit trail database, BAM report data can become stale. This section addresses
EMC Documentum xCP 1.0 Performance Tuning Guide 57