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

Browsers don't show host or very slow refresh #3789

Closed
2 tasks done
mrmagoo1 opened this issue Sep 22, 2023 · 3 comments
Closed
2 tasks done

Browsers don't show host or very slow refresh #3789

mrmagoo1 opened this issue Sep 22, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@mrmagoo1
Copy link

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

the server running on LXC or VM with 4core and 4GB ram on 50Gb ssd disk, when load the first time and add hosts all works good, but after some day ( from 5 to 10) without add any new host, the browser as very slow to view the host or not show any host. I've 150 host on it with only ping setup every 20sec per host.

👟 Reproduction steps

create 4 group and 30host per group, set every single host to ping every 20sec, and add 1-2 tag.
open kuma from Brave, Firefox, Chrome, Safari give same problem after 5-10 days.

👀 Expected behavior

i think it's a problem to load o refresh the page, or db setting.

😓 Actual Behavior

i've to restar from new every time, restore Json or data won't resolve.

🐻 Uptime-Kuma Version

1.23.1

💻 Operating System and Arch

ubuntu - debian - windows10 - macos

🌐 Browser

Chrome, Brave-Latest, Safari-Latest, Firefox

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

@mrmagoo1 mrmagoo1 added the bug Something isn't working label Sep 22, 2023
@CommanderStorm
Copy link
Collaborator

In the v1, the database size heavily grows with number of monitors and retention lenght.
This file-size growth leads to degraded IO-performance.

This issue will be fixed by v2, as #2750 was merged and we support external mariadb.
In v1 you can work around this by sharding (i.e. writing 50 pings/minute to the db) or by lowering the retention period.

Please close this issue, as this is resolved in the next release-train

@mrmagoo1
Copy link
Author

ok thank's,
I'll perform the workaround.
When is schedule the v2 release?

@CommanderStorm
Copy link
Collaborator

When is schedule the v2 release

As with all open-source projects, there is no schedule.
See this milestone for the prgress: https://github.com/louislam/uptime-kuma/milestone/24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants