[jhugo]

We tried to migrate to Gitea at my company, ~100 repositories with a bunch of mirrors, lots of CI, renovate-bot using the API, etc. It was a disaster. It was unusably slow (10+ seconds to load the list of pull requests, API calls to open a new pull request timing out after 60s) despite never using more than a tiny fraction of the resources of a 16-core server. We tried to engage with the community to find out the cause of the slowness and were met with open hostility.

[nine_k]

/* I know it's off-topic, but symptoms look very much like a DNS problem, or a firewall problem. */

[jhugo]

A DNS or firewall problem that causes Gitea to intermittently spend 10+ seconds responding to requests, when running in a cluster alongside other containers that have no such problems? Can you describe a plausible mechanism for that?

We did some profiling and spent quite a bit of time looking at Gitea's source code, it was pretty clear in the end that it's just very very inefficient for large setups. It does an excessive amount of I/O on the Git repositories every time you load a page; there is some caching but not enough / not of the right things. We were really open to implementing fixes and submitting PRs but the community was so hostile that we just abandoned it.

It was overall an enormous waste of time and I can't recommend Gitea to anyone with a setup larger than a handful of small repositories.

[vassilevsky]

I was looking for a simpler GitLab alternative. I guess Gitea is off the list now.

I wonder how CodeBerg works though.