[stevekemp]

Several people have already mentioned that gitlab is slow, so very slow. I've seen replies in this thread that make it obvious that this is being tracked, and that you're well-aware of it.

That said I can't help recalling the last time the topic came up, seven months ago even then it was old-news:

https://news.ycombinator.com/item?id=20995889

If the site hasn't gotten faster in the past year I think it is obvious that this is not a priority in any real sense. Despite claims to the contrary.

Gitlab has a great core-offering, the gitlab runners were wonderful when they came out. But it seems like new features are constantly being piled on top of each release, (time tracking?!) when it might benefit users to step back a little bit and focus upon the core.

I can only assume developers get recognition by new-features, not core-improvements.

[sytse]

Thanks, I agree we should focus more on loading speed and we'll do so in our second fiscal quarter that starts in two weeks https://about.gitlab.com/company/okrs/fy21-q2/

The comment you linked says: "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]."

The current state is that Puma is now powering all of GitLab.com and we're working on getting it to be the default in Omnibus https://gitlab.com/gitlab-org/omnibus-gitlab/issues/4698