Memory Team - 13.10 Planning
Capacity
List any noteworthy PTO that may impact the capacity for the planned milestone
Planning
Indicate major efforts by linking to the appropriate epic. Under each epic indicate who is focusing on these efforts and list the individual issues assigned for this milestone. These will drive which issues are marked as Deliverable. An example of the layout is below
Running GitLab in a memory constrained ENV
Who: @alipniagov @mkaeppler
In %13.10 we will wrap up our efforts in this area. We've delivered individual items throughout %13.9 and will assess there combined impact this release.
- gitlab-org/gitlab#289909 (closed)
- gitlab-org/gitlab#321565 (closed)
- gitlab-org/gitlab#300603 (closed)
Split application into functional parts to ensure that only needed code is loaded with all dependencies
- gitlab-org/gitlab#288044 (closed)
- Deliver an architectural blueprint (issue TBD)
- Measure impact of the proposed changes
Assess features for memory use
With the patched ruby becoming available, we can start gathering data on the memory use of features.
- gitlab-org/gitlab#321528 (closed)
- gitlab-org/gitlab#321527 (closed)
- gitlab-org/gitlab#289844
- gitlab-org/gitlab#321050
Reminder Set Deliverable as the plan for the milestone solidifies. Review during the milestone