Slow startup & Huge CPU usage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Summary

GitLab eats too many CPU resource on start and slow with recommend hardware spec. Installed from official deb package @ 9.0.4

https://docs.gitlab.com/ce/install/requirements.html

This document says 2 core is recommend for < 500 users, this just mean gitlab will work on this spec or slow startup is a bug or can be optimize?

Hardware:

CPU: Intel E5-2620 V4 2 Core (I'm not very sure about this, but performance like this model)

Memory: 8GB

Disk: 30GB Unknow, sequence read and write is fast.

Resource Usage

  • 50 Users

  • 90 Repo (include forks, some are large > 800M, other < 5M, total size 2.8G)

Steps to reproduce

gitlab-ctl restart

What is the current bug behavior?

CPU average load is 4.1 in 7 minutes, service unavailable in 7 minutes with HTTP 502

What is the expected correct behavior?

Should boot quickly with recommend hardware

Relevant logs and/or screenshots

nothing wrong, no log

Results of GitLab environment info

System information

System: Ubuntu 16.04

Current User: git

Using RVM: no

Ruby Version: 2.3.3p222

Gem Version: 2.6.6

Bundler Version:1.13.7

Rake Version: 10.5.0

Redis Version: 3.2.5

Git Version: 2.10.2

Sidekiq Version:4.2.7

GitLab information

Version: 9.0.4

Revision: gitlab-ce@63e052a84aa66041bfc3d8e06395cb9728b5f949

Directory: /opt/gitlab/embedded/service/gitlab-rails

DB Adapter: postgresql

URL: https://example.org

HTTP Clone URL: https://example.org/some-group/some-project.git

SSH Clone URL: git@example.org:some-group/some-project.git

Using LDAP: no

Using Omniauth: yes

Omniauth Providers: bitbucket

GitLab Shell

Version: 5.0.0

Repository storage paths:

- default: /var/opt/gitlab/git-data/repositories

Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/

Git: /opt/gitlab/embedded/bin/git

Edited Aug 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading