Increased memory and CPU usage on 1.23.4

[maxim-mityutko]

Description

I'm observing significant increase in memory and CPU usage by Gitea after upgrading official chart from 10.6.0 (gitea: 1.22.3) to 11.0.0 (gitea: 1.23.4).

The instance is private and I am the only user, it is not exposed to the internet. Basically it is used to sync tabs and bookmarks from the Floccus extension. After the upgrade I had to increase memory limits from 250Mi to 400Mi to avoid OOM exceptions.

Here is my conf and the diagnostics report gitea-diagnosis-20250305-225737.zip

Gitea Version

1.23.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

Running on microk8s cluster.

Database

PostgreSQL

[TheFox0x7]

It's a known issue - same root cause as #31956
The difference in allocated memory is the license classifier

[lunny]

Maybe that feature could be disabled with an option.
ref: #33467

[ExplodingDragon]

@maxim-mityutko 300Mi memory limit appears to be insufficient, as it may lead to Out of Memory (OOM) errors when pushing larger repositories or during git fsck operations. Additionally, while reviewing your kustomization.yaml file, I noticed that your secret is publicly exposed. If this contains actual production credentials, I strongly recommend replacing it immediately.

[maxim-mityutko]

@ExplodingDragon Thanks for pointing this out. It is indeed not enough with the current release of Gitea, and I actually bumped it to 400, but the change is not on main. However the point is that the Gitea's resource consumption went up and as others pointed out above, the reason for this is known.
Regarding the secrets, I use SealedSecrets to encrypt the actual secret. So no actual secret data is exposed. But thanks for mentioning it.

[wxiaoguang]

The "license" memory usage should should have been fixed by Only keep popular licenses #33832 (in the current development branch "main" 1.24)

• https://dl.gitea.com/gitea/main-nightly/
• https://hub.docker.com/r/gitea/gitea/tags?name=nightly

[maxim-mityutko]

Seems to be under control. I'll let it run for now on a nightly build and check the resource usage again after some time.

[maxim-mityutko]

Memory usage looks good after a gew days. Thanks for the quick fix!