search

cachethq / cachet

🚦 The open-source status page system.
https://cachethq.io
MIT License
13.93k stars 1.55k forks source link

Cachet takes FORever to update an incident or status #4147

Closed mfahey79 closed 1 year ago

mfahey79 commented 3 years ago

When you click Submit for a new incident, the browser just spins and in the background it emails each users one by one ever few seconds. Once that process is complete, it then posts the incident on the page. Also, httpd uses 100% cpu regardless of how many cores I give it.

This is strange.

It should post the status/incident immediately then send out the emails. I only have about 50 users signed up and it takes 5 minutes to send these emails. Very strange.

welcome[bot] commented 3 years ago

:wave: Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue. If you're looking for support, you should try the Slack group by registering your email address at https://cachethq-slack.herokuapp.com. Alternatively, email support@alt-three.com for our Professional support service (please note, this a paid service.) If you're issue is with documentation, you can suggest edits by clicking the Suggest Edits link on any page, or open an issue at https://github.com/CachetHQ/Docs

Dozecloud-llc commented 3 years ago

What web server are you using? @mfahey79

benperiton commented 3 years ago

@mfahey79 The sync driver processes the queue in the main thread, so yes it would be slow. You would need to use a different driver, then have a seperate script running to process the queue (kept alive by supervisor or similar)

https://docs.cachethq.io/docs/configuring-the-queue

lol768 commented 3 years ago

any update? Bout to use different software. Your's doesnt work right.

:man_facepalming:

@mfahey79 Bit of friendly advice: no OSS maintainers owe you anything - and you look quite silly when it's readily apparent you've failed to read the documentation and complain about not having received an immediate response.

jbrooksuk commented 1 year ago

Thank you for your input on Cachet 2.x. We are shifting our attention and resources to Cachet 3.x and will no longer be supporting the 2.x version. If your feedback or issue is relevant to the 3.x series, we encourage you to engage with the new branch.

For more information on the Cachet rebuild and our plans for 3.x, you can read the announcement here.

We appreciate your understanding and look forward to your contributions to the new version.