Skip to content
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

DB size #5187

Closed
2 tasks done
jackzVZW opened this issue Oct 11, 2024 · 1 comment
Closed
2 tasks done

DB size #5187

jackzVZW opened this issue Oct 11, 2024 · 1 comment
Labels

Comments

@jackzVZW
Copy link

⚠️ 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
@jackzVZW jackzVZW added the help label Oct 11, 2024
@CommanderStorm
Copy link
Collaborator

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

#3595 might be nessesary to solve the disk size issue though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants