Reviewing performance after development

When you are ready to test the complete system, review its performance in detail.

Take the following steps to complete your performance review:

1. Validate system performance and response times against your performance objectives.
2. Identify resources whose usage requires regular monitoring.
3. Incorporate the observed figures into future estimates:
   1. Identify discrepancies from the estimated resource usage
   2. Identify the cause of the discrepancies
   3. Assign priorities to remedial actions
   4. Identify resources that are consistently heavily used
   5. Set up utilities to provide graphic representation of those resources
   6. Project the processor usage against the planned future system growth to ensure that adequate capacity is available
   7. Update the design document with the observed performance figures
   8. Modify your procedures for making estimates according to what you have learned what you have learned

Results

You need feedback from users and might have to solicit it. Establish reporting procedures, and teach your users how to use them. Consider logging incidents such as:

• System, line, and transaction or query failures
• System unavailable time
• Response times that are outside the specified limits
• Incidents that imply performance constraints, such as deadlocks, deadlock abends, and insufficient storage
• Situations, such as recoveries, that use additional system resources

You should log detailed information for such incidents.

• Time
• Date
• Location
• Duration
• Cause (if it can be determined)
• Action taken to resolve the problem