You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have about 1400 monitors and loading the dashboard is extremely slow, takes about 10-15 seconds. I have a powerful server, 16 vCPU, 64GB RAM. The DB is offloaded to a managed MySQL server (Google Cloud)
I think a lot of the bottleneck seems to be localized on the client side.
All of my tests run every 60 seconds, so nothing super intense on that side, and all are only ping tests.
Looking for anything that can be done to improve the performance, or any updates that can be made to move more of the load to the server side instead of the client side.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
2.0.0-beta.1
💻 Operating System and Arch
Debian 12
🌐 Browser
Chrome Version 133.0.6943.126 (Official Build) (64-bit)
🖥️ Deployment Environment
Runtime: Docker version 20.10.24+dfsg1, build 297e128
Database: Google Cloud MySQL 8.4
Filesystem used to store the database on: N/A
number of monitors: 1400
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
📝 Describe your problem
I have about 1400 monitors and loading the dashboard is extremely slow, takes about 10-15 seconds. I have a powerful server, 16 vCPU, 64GB RAM. The DB is offloaded to a managed MySQL server (Google Cloud)
I think a lot of the bottleneck seems to be localized on the client side.
All of my tests run every 60 seconds, so nothing super intense on that side, and all are only ping tests.
Looking for anything that can be done to improve the performance, or any updates that can be made to move more of the load to the server side instead of the client side.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
2.0.0-beta.1
💻 Operating System and Arch
Debian 12
🌐 Browser
Chrome Version 133.0.6943.126 (Official Build) (64-bit)
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: