sameersbn / sameersbn/docker-gitlab

Performance issue, slow page loading on "project1/-/issues/1" page on GitLab 14.10.2 fresh install

Open
#2,566 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Hi,

I run a fresh, empty GitLab sameersbn/gitlab:14.10.2 instance on this host:

I use this docker-compose.yml configuration (it is a test instance on my local desktop):

version: '3.9'
services:
  postgres:
    image: index.docker.io/postgres:12.4-alpine
    command: >
      -c shared_buffers=2000MB
      -c maintenance_work_mem=150MB
      -c work_mem=50MB
      -c seq_page_cost=0.8
      -c random_page_cost=1.1
      -c effective_io_concurrency=200
    environment:
      POSTGRES_PASSWORD: password
      POSTGRES_USER: gitlab
      POSTGRES_DB: gitlabhq_production
    volumes:
      - ./volumes/postgresql:/var/lib/postgresql/data

...

  gitlab:
    image: sameersbn/gitlab:14.10.2
    ports:
      - "9922:22"
      - 80:80
    environment:
      ....
      PUMA_WORKERS: 32
      PUMA_THREADS_MIN: 1
      PUMA_THREADS_MAX: 16
      PUMA_PER_WORKER_MAX_MEMORY_MB: 8048
      PUMA_MASTER_MAX_MEMORY_MB: 8048
      ...

I created empty issue: http://127.0.0.1/gitlab-instance-71f415c6/project1/-/issues/1

Here is the performance of http://127.0.0.1/gitlab-instance-71f415c6/project1/-/issues/1 page:

Screenshot from 2022-05-22 12-17-11

This page take 857ms, sometime1070ms. 3800ms if I count all page dependencies loading.

This is the HAR file issue1.har, I excluded notes and realtime_changes requests.

This is the performance bar flamegraph in wall mode (issues_1_perf_bar_1653215576325.json) : Screenshot from 2022-05-22 12-31-34

Do you have any idea why this page is so slow to load? Do you have a solution or is it a real GitLab implementation problem?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the docker-compose.yml configuration and reproduce the empty issue page at the reported GitLab URL. Compare issue1.har with the performance-bar flamegraph to isolate the slow request or dependency; done means a reproducible cause and a documented fix or clear evidence that the problem belongs upstream.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, gitlab
Domain
devops, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.