git push and pull often result in 100% CPU usage.

[huyangcheng]

Description

Deployed using Docker, with no special configuration required, using the docker-compose.yml file from the official tutorial

The issue manifests as a single CPU core being at 100% utilization; even after increasing server configuration, multiple cores cannot be utilized, resulting in long wait times for push and pull operations during Git operations due to the 100% CPU usage

docker-compose.yml

`
version: "3"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:1.22.3
container_name: gitea
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000:3000"
`

Currently, only three or four people are using it, with fewer than ten repositories, all of which are typical Node.js projects, and each repository is quite small.

I need to improve its ability to quickly perform Git operations. What are some possible solutions and troubleshooting methods?

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

version: "3"

networks:
gitea:
external: false

services:
server:
image: gitea/gitea:1.22.3
container_name: gitea
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- ./gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000:3000"

Database

None

[techknowlogick]

This is quite unusual, as there are instances with thousands of users on them with similar resources that you have. The first thing to try is to update to the latest stable version (1.25.1 at the time of writing). Please make sure to backup your database, and the other data before upgrading though.