[v2] High CPU usage for Uptime-Kuma while using ping monitors

[n1084ky]

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Hello,

The CPU value for the uptime-kuma installed in docker is very high. The CPU value is always over 100% and the dashboard does not load or the monitored services do not appear. I am running about 60 monitors, a mixture of HTTP and PING.

Do you have any idea how I can fix this problem?

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

latest

💻 Operating System and Arch

ubuntu 22.04

🌐 Browser

chrome

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors: 60

[CommanderStorm]

• Are you running v2 or v1? Depedning on your retention this might be a probelm
• Are you runnning the "real-browser" monitor? [Real Browser] High CPU/Memory Usage #3788

[n1084ky]

i'm running v2 . I am not running the "real-browser" monitor. I noticed that when I used chromium, the cpu usage increased even more and I stopped using it. But now the cpu value is still very high and I usually can't use the dashboard.

[CommanderStorm]

Okay, seems weird.
Lets fill in the blanks

• Runtime?
• Database?
• Filesystem used to store the database on?
• amount of ping monitors?
• how often do the ping monitors ping?
• What hardware are you running it on?

There has also been a report complaining about how CPU intensive ping is, so this might be related. Have not had the time/energy to investigate further

[n1084ky]

Runtime : Docker 24.0.7,
Database : SQLite
Filesystem used to store the database on : ext4
amount of ping monitors : 64
how often do the ping monitors ping : every 20 seconds
What hardware are you running it on : 24 vCPUs, 48GiB RAM

[CommanderStorm]

We should only be able to use 1 vCPU. (node => single threaded)
Is there really no relevant log entrys about what the system is struggling with?

[PikuZheng]

The dashboard often doesn't respond when using Chrome, but will load after some patience. I didn't notice CPU usage, but that has improved in 2.0beta