3 ms·
I think the issue with Gitlab resource usage isn't the application itself, but the sheer complexity of Gitlab and the amount of services needed to run the whole
by Kovah 4y ago
I think the issue with Gitlab resource usage isn't the application itself, but the sheer complexity of Gitlab and the amount of services needed to run the whole thing. It even starts Prometheus and Grafana and stuff like that.
https://docs.gitlab.com/ee/development/architecture.html https://docs.gitlab.com/ee/development/architecture.html
- kardianos 4y agoYes, it is mostly ruby if you profile it.
- nerdponx 4y agoIs it possible to run it under one of the supposedly-faster alternative implementations like TruffleRuby?
- infogulch 4y agoIn general, the larger the project the more likely that all obscure corners of a language are utilized somewhere in the project; these same obscure corners are typically the weakest point of alternative implementations and are likely to cause issues.
- packetlost 4y agoNah, it's definitely Ruby. It uses Postgres + Redis + a S3-like object store for most of the data heavy-lifting. There is some additional ops complexity in Gitaly, their git backend, but that wouldn't be a huge source of resource usage in a simple setup