Memory Team - 13.9 Planning
Capacity & Planning
List individual PTO entries for the current milestone
Links
%13.9
Priorities for In %13.8 we identified the building blocks for memory reduction. %13.9 will include implementation issues. The main goal for this milestone is to have a measurable reduction on the memory footprint of running GitLab in a memory constrained environment.
Reduce Puma's memory footprint
Who: @alipniagov
- Run Puma in Single mode on constrained environments - gitlab-org/gitlab#291064 (closed)
- Run GC compact before forking into Puma workers (nakayoshi_fork) - gitlab-org/gitlab#288042 (closed)
Continued gitlab-exporter optimizations
Who: @mkaeppler
Dependency Loading Optimizations
Who: @nmilojevic1
- Provide mechanism to load GraphQL with all dependencies only when needed - gitlab-org/gitlab#288044 (closed) (potential carry over)
- Split application into functional parts to ensure that only needed code is loaded with all dependencies - gitlab-org/gitlab#290935 (closed) (to be broken down further)
To be reviewed for prioritization (for future milestones)
- Rails takes awhile to boot, let's see if we can improve this gitlab-org/gitlab#213992
- Change
GitLab::LoadBalancing
to use a native Rails implementation for connection handling - gitlab-org/gitlab#296870 - Review (confirm) issues within Drop gitlab-exporter - gitlab-org&5035 that we will own, and those that we will not own.
- Split application into functional parts to ensure that only needed code is loaded with all dependencies - gitlab-org/gitlab#290935 (closed)
- Allow admins to configure rack-timeout for Puma - gitlab-org/charts/gitlab#2191 (comment 482881150)
Reminder Set Deliverable as the plan for the milestone solidifies. Review during the milestone