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 am currently managing a large number of monitors, which could potentially reach 2000 or more. I am seeking advice on which database would be best suited to handle this scale efficiently.
📝 Error Message(s) or Log
no
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
centos 7.9
🌐 Browser
chrome
🖥️ Deployment Environment
Runtime: k8s
Database: sqlite
Filesystem used to store the database on: ssd
number of monitors: 700+
very slow.
The text was updated successfully, but these errors were encountered:
We've recently migrated to 2.0.0-beta.0 and an external MariaDB. Even though it's the first beta we're very happy with it. 1.x was struggling with 40+ monitor and was veeeery slow. The SQLite database got corrupted twice so we had to restore from backups.
The wiki isn't updated yet so we had to look at the code to see how it should be configured.
🛡️ Security Policy
📝 Describe your problem
I am currently managing a large number of monitors, which could potentially reach 2000 or more. I am seeking advice on which database would be best suited to handle this scale efficiently.
📝 Error Message(s) or Log
no
🐻 Uptime-Kuma Version
1.22.1
💻 Operating System and Arch
centos 7.9
🌐 Browser
chrome
🖥️ Deployment Environment
very slow.
The text was updated successfully, but these errors were encountered: