High CPU Usage and Log Overflow with Frequent FetchTask Requests from Multiple Runners in Gitea Actions

[yanhao98]

Description

I am experiencing significant issues with Gitea Actions in a setup involving a large number of runners (60 machines). These runners are making requests to /api/actions/runner.v1.RunnerService/FetchTask at a very high frequency, which is leading to two major problems:

High CPU Usage on Gitea Server: The frequent requests from these numerous runners are causing an excessively high CPU usage on my Gitea server. This is concerning as it affects the overall performance and responsiveness of the server.

Log File Overload: My server logs are being overwhelmed with entries related to FetchTask. The sheer volume of these log entries is making it difficult to track other important logs and potentially masking other crucial information.

I am seeking guidance or a solution to mitigate these issues. Ideally, I am looking for a way to manage the frequency of these FetchTask requests or any other recommendation that could help in optimizing the performance and log management under such a scenario.

Gitea Version

1.21.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

PostgreSQL

[wolfogre]

May be related to #24543.

[yanhao98]

May be related to #24543.

Okay, I'll close this issue.