3 ms·
They have a dedicated section about performance improvements in the release notes. It links to a list of 53 commits from this release targeting performance: h
by scottfr 8y ago
They have a dedicated section about performance improvements in the release notes.
It links to a list of 53 commits from this release targeting performance:
https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&label_name%5B%5D=performance&milestone_title=10.7 https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=...
- sytse 8y agoThanks Scott for linking to that. We're very much trying to improve the performance of GitLab. I do think that most of our performance improvements are to improve the end-user experience. So I totally understand dijit's request to reduce memory. Today we recommend 4GB of memory to run GitLab https://docs.gitlab.com/ee/install/requirements.html#memory https://docs.gitlab.com/ee/install/requirements.html#memory One big thing would be if we can run the Ruby code multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 You can see I created that issue 2 years ago and there has been recent activity on it. Right now GitLab the company is focussed on making complete DevOps https://about.gitlab.com/2017/10/11/from-dev-to-devops/ https://about.gitlab.com/2017/10/11/from-dev-to-devops/ happening. So any help on the multi-threading is appreciated. The first thing would be to implement https://github.com/covermymeds/rubocop-thread_safety https://github.com/covermymeds/rubocop-thread_safety