4 ms·

>Speed. The GitLab web interface has always felt sluggish to me. 10 years later the same problem remains. While Gitea / Forgejo have very little performance pr

by ksec 9mo ago

>Speed. The GitLab web interface has always felt sluggish to me. 10 years later the same problem remains. While Gitea / Forgejo have very little performance problems. And will only get better once Go 1.26 is out. Which is a much bigger release than a single digit version number upgrade.

sschueller 9mo ago
I just wish they had sub/project folders like in gitlab. I would switch in a heartbeat.
dewey 9mo ago
Just like a truck will always be more sluggish than a small car. They are very different beasts where one is aimed at enterprises and the other one for small projects without all the corporate needs.
- pornel 9mo ago
  The enterprise version is just as slow. I thought they're only struggling with the free public version, but no. GitLab run on a private box is the same bag of lags and loading spinners.
  - dewey 9mo ago
    I'm not talking about GitLab enterprise vs. GitLab free. It's about GitLab vs small projects like Gitea / Forgejo mentioned in the parent comment.
    - WD-42 9mo ago
      "It's enterprise" it's such a lame excuse, IMO. There shouldn't be a speed tax, especially if you aren't using the "enterprise" features. We need to stop making excuses for bad software. It's 2026 we have insanely powerful computers, why should I have to wait to get the result of searching a few text-only issues or display a diff?
      - vardalab 9mo ago
        Yea, I run my own gitea in the basement proxmox box to have a decent performance. Page load times are <30ms
        iamcreasy 9mo ago
        Curious, why not use docker?
        vardalab 9mo ago
        I like LXC containers and how they integrate with PBS.
- oivey 9mo ago
  A truck is sluggish because of its weight and inertia. It’s a law of nature. What law of nature is making Gitlab slow?
WA 9mo ago
I used GitLab only as a remote repo for private projects, no CI at all. The laggy interface and that damn browser check every so often made me close my account.
WD-42 9mo ago
It must be a fundamental architectural problem with Gitlab. When I had to use it for work the speed killed me. Especially searching for issues. I will never consider gitlab for anything until they find a way to boost performance.
- jeremyjh 9mo ago
  The Ruby on Rails tax. It isn’t impossible to make snappy apps with it, but it must be uneconomical in terms of dev costs because no one does.
  - ksec 9mo ago
    I dont think that is true, consider Fuzzy, Hey, Basecamp, Shopify all seems to be doing fine. Shopify actually got impressively fast in the recent two years I have no idea why. Github used to be fast as well. So while Go by default will always be faster then Ruby Rails, there are plenty of examples of decently fast Ruby Rails Apps. Having 10 years saying they will improve performance and not getting any of it suggest problems with Gitlab itself more than RoR.
    - DoctorOW 9mo ago
      > consider Hey, Basecamp, Shopify Basecamp is slow as hell, Shopify depends on some insanely specific tuning, and I don't use Hey but it's the same team as Basecamp IIRC.
  - 12_throw_away 9mo ago
    > The Ruby on Rails tax. Yeah, from my experience administering a pretty small self-hosted instance, I think it's got to be this. Every single admin action you try to take on the backend is SLOWWWWW. Restarting the services takes a few minutes. Just to bring up an admin console on the server in a CLI takes well over a minute, which indicates a tremendous amount of overhead purely on the ruby side. There's just something fundamentally slow about how it's all put together. I wouldn't blame the language or tech stack, exactly - but perhaps Ruby on Rails is not a great fit, anymore, for a fully featured forge of this scale?
quaintdev 9mo ago
> And will only get better once Go 1.26 is out. Can anyone tell me why? What's changing with Go 1.26?
- ksec 9mo ago
  Go 1.26 Is Around the Corner: Small Changes, Big Impact for Real-World Go Systems https://medium.com/@anand.hv123/go-1-26-is-around-the-corner-small-changes-big-impact-for-real-world-go-systems-b7e5bd271f51 https://medium.com/@anand.hv123/go-1-26-is-around-the-corner...
  - 306bobby 9mo ago
    https://freedium-mirror.cfd/https://medium.com/@anand.hv123/go-1-26-is-around-the-corner-small-changes-big-impact-for-real-world-go-systems-b7e5bd271f51 https://freedium-mirror.cfd/https://medium.com/@anand.hv123/...
deleted 9mo ago
[deleted]
usr1106 9mo ago
Very weird, my experience is the opposite. When changing jobs in 2018 I moved from Bitbucket and Confluence (own data center, but to my understanding powerful and well-maintained) to Gitlab cloud. Atlassian was laggy, overengineered and not pleasant to use. Gitlab was slim and fast. They have added a lot of stuff since then and maybe smreponsiveness has suffered a bit, but I can't really complain. Gitlab works well most of the time. Recently I have had to use Jira cloud. Much worse than Gitlab. Could be that our templates are overloaded and some extensions are particularly bad (looking at you XRay). But pretty sluggish and annoying user experience. With Gitlab over-excited managers cannot ruin performance by having more and more details added to the templates.
- davorak 9mo ago
  jira, bitbuck, etc historically and currently are all slow(still faster than they used to be, considerably so). So in comparison to a set of tools I have always seen talked about as slow, gitlab is faster.
estimator7292 9mo ago
Simply having CI/CD enabled causes GitLab to use most of one CPU core... forever. It's astonishing.

by ksec 9mo ago

sschueller 9mo ago

I just wish they had sub/project folders like in gitlab. I would switch in a heartbeat.

dewey 9mo ago

Just like a truck will always be more sluggish than a small car. They are very different beasts where one is aimed at enterprises and the other one for small projects without all the corporate needs.

pornel 9mo ago
The enterprise version is just as slow. I thought they're only struggling with the free public version, but no. GitLab run on a private box is the same bag of lags and loading spinners.
- dewey 9mo ago
  I'm not talking about GitLab enterprise vs. GitLab free. It's about GitLab vs small projects like Gitea / Forgejo mentioned in the parent comment.
  - WD-42 9mo ago
    "It's enterprise" it's such a lame excuse, IMO. There shouldn't be a speed tax, especially if you aren't using the "enterprise" features. We need to stop making excuses for bad software. It's 2026 we have insanely powerful computers, why should I have to wait to get the result of searching a few text-only issues or display a diff?
    - vardalab 9mo ago
      Yea, I run my own gitea in the basement proxmox box to have a decent performance. Page load times are <30ms
      - iamcreasy 9mo ago
        Curious, why not use docker?
        vardalab 9mo ago
        I like LXC containers and how they integrate with PBS.
oivey 9mo ago
A truck is sluggish because of its weight and inertia. It’s a law of nature. What law of nature is making Gitlab slow?

WA 9mo ago

I used GitLab only as a remote repo for private projects, no CI at all. The laggy interface and that damn browser check every so often made me close my account.

WD-42 9mo ago

It must be a fundamental architectural problem with Gitlab. When I had to use it for work the speed killed me. Especially searching for issues. I will never consider gitlab for anything until they find a way to boost performance.

jeremyjh 9mo ago
The Ruby on Rails tax. It isn’t impossible to make snappy apps with it, but it must be uneconomical in terms of dev costs because no one does.
- ksec 9mo ago
  I dont think that is true, consider Fuzzy, Hey, Basecamp, Shopify all seems to be doing fine. Shopify actually got impressively fast in the recent two years I have no idea why. Github used to be fast as well. So while Go by default will always be faster then Ruby Rails, there are plenty of examples of decently fast Ruby Rails Apps. Having 10 years saying they will improve performance and not getting any of it suggest problems with Gitlab itself more than RoR.
  - DoctorOW 9mo ago
    > consider Hey, Basecamp, Shopify Basecamp is slow as hell, Shopify depends on some insanely specific tuning, and I don't use Hey but it's the same team as Basecamp IIRC.
- 12_throw_away 9mo ago
  > The Ruby on Rails tax. Yeah, from my experience administering a pretty small self-hosted instance, I think it's got to be this. Every single admin action you try to take on the backend is SLOWWWWW. Restarting the services takes a few minutes. Just to bring up an admin console on the server in a CLI takes well over a minute, which indicates a tremendous amount of overhead purely on the ruby side. There's just something fundamentally slow about how it's all put together. I wouldn't blame the language or tech stack, exactly - but perhaps Ruby on Rails is not a great fit, anymore, for a fully featured forge of this scale?

quaintdev 9mo ago

> And will only get better once Go 1.26 is out. Can anyone tell me why? What's changing with Go 1.26?

ksec 9mo ago
Go 1.26 Is Around the Corner: Small Changes, Big Impact for Real-World Go Systems https://medium.com/@anand.hv123/go-1-26-is-around-the-corner-small-changes-big-impact-for-real-world-go-systems-b7e5bd271f51 https://medium.com/@anand.hv123/go-1-26-is-around-the-corner...
- 306bobby 9mo ago
  https://freedium-mirror.cfd/https://medium.com/@anand.hv123/go-1-26-is-around-the-corner-small-changes-big-impact-for-real-world-go-systems-b7e5bd271f51 https://freedium-mirror.cfd/https://medium.com/@anand.hv123/...

deleted 9mo ago

[deleted]

usr1106 9mo ago

Very weird, my experience is the opposite. When changing jobs in 2018 I moved from Bitbucket and Confluence (own data center, but to my understanding powerful and well-maintained) to Gitlab cloud. Atlassian was laggy, overengineered and not pleasant to use. Gitlab was slim and fast. They have added a lot of stuff since then and maybe smreponsiveness has suffered a bit, but I can't really complain. Gitlab works well most of the time. Recently I have had to use Jira cloud. Much worse than Gitlab. Could be that our templates are overloaded and some extensions are particularly bad (looking at you XRay). But pretty sluggish and annoying user experience. With Gitlab over-excited managers cannot ruin performance by having more and more details added to the templates.

davorak 9mo ago
jira, bitbuck, etc historically and currently are all slow(still faster than they used to be, considerably so). So in comparison to a set of tools I have always seen talked about as slow, gitlab is faster.

estimator7292 9mo ago

Simply having CI/CD enabled causes GitLab to use most of one CPU core... forever. It's astonishing.