How to improve performance of uptime kuma

[mabed-fr]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

My problem is not a very important problem, but i constate for print chart is too slow, i see a external SQL integration feature for 2.0 is in progress.

After a lot of reviews of type of database a NoSQL database is not more adapted ? the write and read is very very more performant is NoSQL, and Nosql can manage internal data of uptime kuma and result of check.

Other idea is to use SQL for the part of authentification and internal data for uptime kuma and TSDB for register heath check result , this solution is more complicated but more performant also.

Enjoy discute with you !

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

2.0.0

💻 Operating System and Arch

Debian 11

🌐 Browser

Chrome

🐋 Docker Version

Docker

🟩 NodeJS Version

No response

[CommanderStorm]

See #3017
See #2750