Memory Team - 13.6 Planning Issue
Capacity & Planning
Out of XX business days between Sept 18 - Oct 17 ~95%
List individual PTO entries below
Links
%milestone
Priorities for High
-
Wrap up issues in
- Dynamic Image Resizing: Implementation to deployment - gitlab-org&4423 (closed)
- Investigate and reduce end-points with biggest amount of CACHE SQL calls - gitlab-org&4508 (closed)
-
Running GitLab in a memory constrained environment - gitlab-org&448 (closed)
- Initialisers that reconfigure working environment should use LifecycleEvents - gitlab-org/gitlab#215318
- Investigate Impact of Using Ruby 2.7 on Memory Usage - https://gitlab.com/gitlab-org/memory-team/team-tasks/-/issues/45
- Review Stan's notes on Ruby 2.7 so far gitlab-org&2380 (comment 426647705)
Medium
- All issues in Memory Team - FY21-Q3 Memory Group Lessons Learned and Knowledge Sharing from Performance Improvements - https://gitlab.com/groups/gitlab-org/memory-team/-/epics/1
- Let's review each issue to see if they provide value
- Implement those that do provide value
- Finish up Image Resizing blog post
- Document Lessons learned in Cached SQL Calls
- Anything else noteworthy of a handbook or blog post
Stretch Goals
Reminder Set Deliverable as the plan for the milestone solidifies. Review during the milestone
Edited by Craig Gomes