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 catch and repair issues before they become widespread, we can save time and money. We started that conversation with baselines for various artifacts and factors for baselines.
Baselines lead to maintaining performance history for trends and spotting anomalies. When problematic content is identified, the recommendation for remediation work is prioritized based on business value and use impact. That investment involves metrics and tools we described in previous chapters to profile systems and slow areas. We then learned about taking lessons from any fixes back into standards and common practices to reduce future issues.
The chapter then transitioned to ways to share knowledge and awareness of performance issues with the developer community and how to leverage guidance documentation...
