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

Experience with PHP-FPM and mariadb heigh load #9620

Closed
ufgum opened this issue May 1, 2024 · 0 comments
Closed

Experience with PHP-FPM and mariadb heigh load #9620

ufgum opened this issue May 1, 2024 · 0 comments

Comments

@ufgum
Copy link

ufgum commented May 1, 2024

Steps to reproduce

I have various IMAP accounts with a total of around 200,000 emails. Since the last update, the mail app is hardly usable anymore because when you call up the mariadb server works long time until the server can hardly be reached anymore. The server isn't super fast because it's an Intel NUC, but it's always been sufficient so far.
If I run an "occ mail:account:sync" on my accounts, I can use the Mail APP again for about a day. The cron jobs also run reliably, nothing has changed so far.

My problem now is that I did a Debian update from 10 to 12, so I also switched from PHP to PHP-FPM with opcache, and immediately afterwards did a Nextcloud with Mail APP update. So of course all traceability is lost.

However, I strongly suspect PHP-FPM and wanted to ask if anyone has any experience comparing the mail APP with PHP or PHP-FPM in relation to mariadb utilization?

Expected behavior

less db activity

Actual behavior

heavy db activity

Mail app version

3.6.0

Mailserver or service

dovecot on same machine

Operating system

debia 12

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database

MariaDB

Additional info

No response

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

No branches or pull requests

1 participant