Document step by step process to solving performance problems
To prevent developers from playing tug-o-war with those working on improving performance we have to set up/document a step by step plan on solving performance problems. From the top of my head this plan is fairly simple:
- Describe the problem in the form of an issue with logs, whatever existing metrics are available and ideally a way to reproduce the problem.
- Make sure the code involved is adequately instrumented using GitLab Performance Monitoring
- Deploy the instrumentation to GitLab.com and let it run for at least 24 hours
- Work on actually improving any code in question
- Deploy to GitLab.com, let it run for 24 hours
- Rinse and repeat
@joshfng @rspeicher @pcarranza @DouweM: Any suggestions?