sameersbn / sameersbn/docker-gitlab
Help on configuration parameters
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 have a lot of problems with my gitlab instance. It is very slow.
I installed the last release 16.0.1.
My server (Virtual Machine, VMWare Fusion, Docker, Ubuntu 22) has :
- 8CPU
- 16Gb RAM
- About 100 users
- About 30 simultanous jobs
Do you have any configuration advice for the following parameters:
- PUMA_WORKERS=6
- PUMA_TIMEOUT=90
- PUMA_THREADS_MIN=8
- PUMA_THREADS_MAX=8
- PUMA_PER_WORKER_MAX_MEMORY_MB=1024
- PUMA_MASTER_MAX_MEMORY_MB=2048
- SIDEKIQ_CONCURRENCY=20
- SIDEKIQ_SHUTDOWN_TIMEOUT=4
- GITLAB_RAILS_RACK_TIMEOUT=600
I tried a lot of values, but never better. Can you help me?
Thanks in advance
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are identified. Start by reviewing the listed Puma, Sidekiq, and Rails timeout parameters in the Dockerized GitLab configuration and the reported resource limits. Done would require a clearly scoped, reproducible performance diagnosis or documented configuration guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100