Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #49702

Closed
Open
Opened Jul 27, 2018 by Tommy Morgan@tommy.morgan
  • Report abuse
  • New issue
Report abuse New issue

Investigate memory consumption for GitLab unicorn processes

We want to reduce GitLab's memory consumption. In order to do that we first need to profile our primary processes and determine where our best opportunities are for improvement. @stanhu is going to perform this analysis and suggested that we approach this on three fronts:

  • Unicorn (this issue)
  • Sidekiq (#49703 (moved))
  • Gitaly (gitaly#1298)

I'm creating these issues so we can track our findings and create related issues for specific fixes.

Edited Jul 27, 2018 by Tommy Morgan

Related issues

  • Discussion
  • Designs
Assignee
Assign to
12.5
Milestone
12.5
Assign milestone
Time tracking
None
Due date
None
5
Labels
Memory [DEPRECATED] P3 devops::enablement group::memory memory usage
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-foss#49702