11. Performance Engineering
Maturity Level 2 – Goal oriented
Proactive
Reactive
• Initial :
• Aspirational goals
• Limited storage, visualization
• Data not JOIN’d and not defined
• Eventual:
• Storing everything
• Everyone is using the dashboard
• Exit:
• Regular Reviews and faster troubleshooting
• Relapse:
• Too lenient on ship goals
• Not watching the changes
Measure
Everything
18. Performance Engineering
Maturity Level 3 – Under Control
Proactive
Reactive
• Initial :
• 3 steps forward, 1 step back
• Cant get at the data fast enough (hours)
• Eventual:
• Dynamic threshold math
• Inline anomaly detection for production
• Catching bad perf before production
• Exit:
• Cross-Org communications
• Relapse:
- Alerting complexities
- Improper hand-off of Alerts
Measure
Everything
Automate
Everything
23. Performance Engineering
Maturity Level 4 – Best of Breed
Proactive
Reactive
• Initial :
• Everyone is involved, no one owns it
• Super complex
• Putting off for years major architectural
issues
• Eventual:
• Everyone bought into the big event
• and in lock-step
• Exit:
• 3-5 year arc per product group
• Relapse:
- New products
Measure
Everything
Automate
Everything
Communicate
With Everyone
What does a site look like that is not optimized.
Here’s an example.
The main take away here. Is you don’t need every file to load before rendering. Prioritize the download.
Defer all tags and any scripts not needed for rendering
Here’s an example of a waterfall. Our Godaddy home page.
…review the bullets.