News for hackers. Stuff that matters.
Re:Gitea: Open source, self-hosted GitHub alternative by sytse on Sunday May 06, 2018 @03:57PM (#17008158)
Thanks for posting. HA is a paid feature of GitLab and will likely stay a paid feature.

We're working hard on a cloud native alternative to the docker container that works well on Kubernetes. There is more information on https://gitlab.com/charts/gitlab/ and you can see the activity on https://gitlab.com/charts/gitlab/commits/master Since it is cloud native I assume it will allow autoscaling and it neatly orders every component in its own container.

Today GitLab is using a lot of RAM and the best way to reduce that is to make the application server multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 The first priority is to add rubocop rules for https://github.com/covermymeds/rubocop-thread_safety There is a WIP merge request in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1899 Any help is appreciated.

Re:Gitea: Open source, self-hosted GitHub alternative by merb on Sunday May 06, 2018 @05:15PM (#17008584)
> Today GitLab is using a lot of RAM and the best way to reduce that is to make the application server multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592

how is multi-threading helping with memory consumption?

Re:Gitea: Open source, self-hosted GitHub alternative by sytse on Sunday May 06, 2018 @05:57PM (#17008814)
Because the Rails application server is currently single threaded it forks multiple processes that each take up about half a gigabyte of RAM. Running fewer processes would cause increased latency for users.
Re:Gitea: Open source, self-hosted GitHub alternative by jorams on Sunday May 06, 2018 @05:56PM (#17008812)
In a multi-threaded program, the threads share memory. Currently the application server is running in multiple processes, each of which contains a full copy of the core application.