sameersbn / sameersbn/docker-gitlab
Openshift 4 | >10s to git push
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've been using this community gitlab image for about 2y now. Most of that time, gitlab was on openshift 3.
For internal bad reasons, we had to move it out and run on docker.
Now, I need to get it back into openshift, ocp4 to be exact. It's almost a succes, except for the "git push" part.
On an empty gitlab, with lots of RAM and CPU, on a fast storage, a simple "hello world" kind of git push takes at least 10s.
I've watch logs, and nothing helps there.
I've tried many images, and the issue seems to appear when unicorn was replaced by puma.
Is there a way to use recent images (13.x) with unicorn ?
Has anyone ever encounter this kind of issue ?
Is 15s ok for a git push ?
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 entry points are named. Start by reproducing the >10-second git push on OpenShift 4 and comparing the Puma-based 13.x images with the earlier Unicorn setup; done means isolating a documented configuration or image cause, or establishing that the latency is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- devops, infrastructure, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100