gitea: Performance regression on v1.9+

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

Image 2019-08-18 at 19 30 54

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 32 (16 by maintainers)

Most upvoted comments

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] set ENABLE_PPROF=true

then

wget -O cpuprofile.out http://localhost:6060/debug/pprof/trace?seconds=30 

will grab a cpuprofile that can be examined with

go tool pprof --http :8080 cpuprofile.out

There are other profiles including http://localhost:6060/debug/pprof/heap that 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, NOT gitea hook or gitea serv.

If you only have one gitea web site, you should only see ONLY one gitea web process but not 4 instances. That should some scripts configuration error I think.