15.1 Memory retrospective
This is an asynchronous retrospective for the 15.1 release, following the process described in the handbook.
This issue is private (confidential) to the Memory group, plus anyone else who worked with the group during 15.1, to ensure everyone feels comfortable sharing freely. On 2022-06-26, in preparation for the R&D-wide 15.1 Retrospective, the issue will be opened up to the public, as long as everyone is comfortable with this. You're free to redact any comments that contain information that you'd like to stay private before that date.
Please look at back at your experiences working on this release, ask yourself
For each point you want to raise, please create a new discussion with the relevant emoji, so that others can weigh in with their perspectives, and so that we can easily discuss any follow-up action items in-line.
If there is anything you are not comfortable sharing here, please message your manager directly. Note, however, that 'Emotions are not only allowed in retrospectives, they should be encouraged', so we'd love to hear from you here if possible.
Issues we shipped
Deliverables (closed issues with ~Deliverable label for 15.1 milestone):
No deliverables
All closed issues (within 15.1 milestone)
Issues that slipped
- Collect jemalloc stats
- Identify useful diagnostic reports
- Upload diagnostic reports to GCS
- Sidekiq diagnostic reports
- Puma diagnostic reports
- Removal of UI Toggle to Enable / Disable Prometheus in Metrics and Profiling
- Determine current service levels in logs for success rate
- Determine current service levels in logs for latency
- Test main branch against Ruby 3 in a scheduled pipeline
- Default Puma per_worker_max_memory_mb is too low (>13.5)
- Total deliverables closed: 0
- Total issues closed: 11
- Total MRs merged: 19