Thanks for the feedback. We are working hard to improve performance and memory consumption of GitLab. We have two major projects underway, switching to Puma [1] as well as reducing the overall memory consumption of GitLab [2].

You can follow along on some of the progress we are making in each release post in the "Performance Improvements" section. For 12.2 you can see we had 58 MR's related to performance.

[1] - https://docs.gitlab.com/omnibus/settings/puma.html

[2] - https://about.gitlab.com/handbook/engineering/development/en...

[3] - https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=...

I've heard this from gitlab employees before.

Every. Single. Release. For. The. Past. Two. Years.

At some point it seems clear that despite statements to the contrary the speed of the instance, and the resource consumption just cannot be a concern.

I'd rather the core was speedy and resource-appropriate than see additional half-working features bolted on non-stop, while bug reports languish.

Hello! We haven't been at the capacity employee-wise to have teams dedicated to improve much in these areas, but we tripled our employee count this year and have since spun up a memory team [1] and are able to dedicate more people to performance [2]. So hopefully we won't be saying this for much longer!

---

[1] (same link as #2 above) https://about.gitlab.com/handbook/engineering/development/en...

[2] https://about.gitlab.com/handbook/engineering/performance/