gitea: Performance regression on v1.9+
- Gitea version (or commit ref): 1.9.0 (official release)
- Git version: 2.17.1
- Operating system: Ubuntu 18
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
- Log gist: https://gist.github.com/issmirnov/3d317a552d4d485b15519b4ed17c045a
Description
Hey folks. My server ($5 digital ocean droplet, 1vCPU 1gb RAM) has been really struggling with the latest gitea release. Up to v1.7/1.8 or so it was completely fine. Since installing v1.9, htop and other tools consistently show the gitea web process eating up a combined 80% of my CPU.
Are there any performance regression tests for gitea? These recent changes are having a major impact on my entire server, whereas previously it coexisted fine with about 30 services.
Looking at the logs, I do see tons of runtime errors. Unsure if this is related.
Thanks so much - really love gitea, and would love to see the resource usage become normal again.
Screenshots
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 32 (16 by maintainers)
Do you have the repo indexer enabled? If yes, it could be the cause. After it’s done updating the index, CPU should go to idle levels.
Not sure if it helps, but freshly installed gitea on pi 4 constantly eats 5% cpu (no repositores created) Looks like too much
In app.ini:
[server]setENABLE_PPROF=truethen
will grab a cpuprofile that can be examined with
There are other profiles including
http://localhost:6060/debug/pprof/heapthat gives us a memory dump.It would also be helpful to know what are kind of machine you running gitea on? What DB? Are you using repo indexing? Are your repo stats up-to-date? Are you running out of memory? And so on - but the cpuprofile would no doubt be helpful.
Yes, I mean only one
gitea web, NOTgitea hookorgitea serv.If you only have one gitea web site, you should only see ONLY one
gitea webprocess but not 4 instances. That should some scripts configuration error I think.