Summary

In this chapter, we introduced a repeatable process to help you manage performance pro-actively in your organization. This is important for consistency and the overall satisfaction of users. If we can catch and repair issues before they become widespread, we can save a lot of time and money.

We looked at how to establish baselines as a starting point and how it's important to have the correct granularity of model, report page, timeframe, user permissions, and other factors for the baselines. We talked about maintaining performance history so that you can establish meaningful trends and spot seasonal issues. When problematic content is identified, we recommended that the remediation work is prioritized based on business value and user impact to maximize return on investment. That investment involved metrics and tools we described in previous chapters that help profile the system and highlight slow areas. We then learned that taking learnings from any fixes back into...