-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uptime kuma 100% usage of cpu #4094
Comments
You can post the container logs, the output of |
*also include the retention time you configured |
is retention will cost the CPU ? and also i used docker as main platform for deploy kuma. |
@syamsullivan please give us the information we asked for.
Retention is not a likely culprit. Please report it anyway.
Depends what you set your limits to. One CPU is the max node should use. |
I have the same problem. |
@bmdbz
Note that the first beta of v2.0 is still a few weeks out, but said release will come with a lot of performance improvements. |
Thank you for your reply.
In v1, 500+ means more than 500. |
missed this response. |
We are clearing up our old |
The problem still exists |
This is likely resolved by the performance improvement in #4500, more specific #3515 Testing PRs can be done via https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests, but I don't expect that due to you needing to create 500 monitors without good import/export functionality. I have changed this to a FR to avoid stalebot doing shit. What I need from the others in this issue (@sunlewuyou @cayenne17) is the metadata about
|
how many monitors do you have configured ? what is their type ? what is your retention ? |
Since Proxmox is used; Just some questions on terminology: you are using a VM - not an LXC, correct? In any case, CPU usage by default in Proxmox is not exclusive. You can assign CPU resources exclusively / reserved for a VM/LXC then you will not have this issues. To mitigate this and ensure more predictable CPU usage, you can: Set CPU Affinity (Exclusive CPU Allocation):
Limit CPU Usage:
|
🛡️ Security Policy
📝 Describe your problem
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
70b8a69b1ae8 uptime-kuma-saas 103.76% 133.9MiB / 7.637GiB 1.71% 991kB / 8.08MB 41kB / 129MB 12
i have issue with uptimekuma that used only single core, then affected performance dashboard
any suggestion
im using docker
Docker version 24.0.5, build ced0996
centos 7
with 8 cores 8G
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
CentOS Linux release 7.9.2009
🌐 Browser
Version 117.0.5938.88
🐋 Docker Version
Docker version 24.0.5
🟩 NodeJS Version
No response
The text was updated successfully, but these errors were encountered: