Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5316

Closed
Open
Created Oct 11, 2013 by Administrator@rootOwner

High cpu usage / long waiting time for unicorn when viewing large commits

Created by: tomplast

At work we are using GitLab and whenever we try to look at a large commit unicorn get a very high cpu usage and we have to wait a long time for the page to render.

Took one of our larger commits and we had to wait 30 seconds for the commit to load in GitLab. The commit had the following changes: "20 changed files with 4657 additions and 4 deletions"

I have also configured unicorn to spawn more workers but only one of the workers does any job (from the looks of the cpu usage).

Our GitLab instance is virtualized, has 2 cpu cores and about 4GB of memory.

Assignee
Assign to
Time tracking