Why we created a Memory team at GitLab

What this post added

This post details the creation of the GitLab Memory team to address the application's high memory footprint. It outlines the team's priorities: migrating from Unicorn to Puma, optimizing endpoints, and improving development practices. The post specifically highlights the migration from Unicorn to Puma as a key initiative to reduce memory usage, with preliminary research showing Puma's threaded nature requires less memory than Unicorn's single-request-per-process model. The team has configured Puma on dev.gitlab.com and plans to enable it on GitLab.com. Additionally, the team is addressing memory issues in Sidekiq, project import, and exports, and is working on improving internal development practices related to memory usage and code complexity.