DB size #3657

Closed
opened 2026-02-28 03:36:52 -05:00 by deekerman · 1 comment
Owner

Originally created by @jackzVZW on GitHub (Oct 11, 2024).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hi there,
1.23.13 here.
current kuma.db is 6GB, with 200 monitoring targets (PING only). Is it normal?
Keep 90 days monitoring history.

Thanks.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Rocky Linux 9.4

🌐 Browser

Chrome latest

🖥️ Deployment Environment

  • Runtime: node 16.20.2
  • Database: default
  • Filesystem used to store the database on: linux file system
  • number of monitors: 200
Originally created by @jackzVZW on GitHub (Oct 11, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Hi there, 1.23.13 here. current kuma.db is 6GB, with 200 monitoring targets (PING only). Is it normal? Keep 90 days monitoring history. Thanks. ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1.23.13 ### 💻 Operating System and Arch Rocky Linux 9.4 ### 🌐 Browser Chrome latest ### 🖥️ Deployment Environment - Runtime: node 16.20.2 - Database: default - Filesystem used to store the database on: linux file system - number of monitors: 200
deekerman 2026-02-28 03:36:52 -05:00
  • closed this issue
  • added the
    help
    label
Author
Owner

@CommanderStorm commented on GitHub (Oct 11, 2024):

Yes, this is normal.
Please see #4500 for the things that we are doing to aleviate that performance problem and for remidies for this.

https://github.com/louislam/uptime-kuma/pull/3595 might be nessesary to solve the disk size issue though.

@CommanderStorm commented on GitHub (Oct 11, 2024): Yes, this is normal. Please see #4500 for the things that we are doing to aleviate that performance problem and for remidies for this. https://github.com/louislam/uptime-kuma/pull/3595 might be nessesary to solve the disk size issue though.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3657
No description provided.