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
  • #9473

Closed
Open
Created Jul 22, 2015 by Administrator@rootOwner

Slow performance with 16,000 commits / 16,000 tags

Created by: linagee

I have a repo that has about 16,000 commits and 16,000 tags. When I pull it up in GitLab, it takes around 10 seconds to render the commits page and 4 seconds to render the tags page. Is there any way to get this to come up faster? Looking at 'top' inside the server, it seems the problem is one ruby process on one core using 100% cpu. (Looks like a unicorn worker.) The server is using an AMD Phenom II X4 975. If I were to switch to an Intel Core i7-4790K which apparently has better single core performance, do you think I would see an improvement? Is there anything I can tune anywhere that would help? It does not appear to be running out of RAM and it has 8GB available. It does not appear to be I/O bound looking at iowait. Thanks.

edit: It seems that the commits page I was pulling up only lists 40 commits. So, this command should emulate what its doing: (I've set my git pager to cat) Not sure why this takes about a second where GitLab takes 10x as long to display the same thing?

time git log --all --oneline -n 40 >/dev/null

real    0m0.895s
user    0m0.868s
sys 0m0.028s
Assignee
Assign to
Time tracking