sameersbn / sameersbn/docker-gitlab
number of sidekiq workers
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
We are running gitlab on a low scale, thus we do not need 25 sidekiq workers (as they have a quite high memory load). So far there is only an option to configurate UNICORN_WORKERS and NGINX_WORKERS. It would be nice to have an option for the number of sidekiq workers as well.
This issue was alread discussed here: http://serverfault.com/questions/538644/25-sidekiq-processes-for-gitlab
Thanks!
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
Start by locating the existing UNICORN_WORKERS and NGINX_WORKERS configuration and then inspect how Sidekiq processes are launched. Done means the Sidekiq worker count can be configured for low-scale deployments and the configured value is used when the container starts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100