Hi everyone! Hope all is well with y’all…
I am struggling quite a bit with the Reporting features in my 5.2.3 install. Small sends (Less than 2-3K) generate fine, but we have a newsletter list that is ~320K contacts which seems to push Reporting to failure more often than not…
My Mautic version is: 5.2.3
My PHP version is: 8.1 (FPM)
My Database type and version is: AWS RDS (MariaDB 10.6)
Your problem
Reports are extremely slow to load and often time out completely,especially when including columns like “Subject” in email reports. The /s/emails/view/{id} pages can take 5–13 minutes to load or fail to render entirely. Exporting those reports sometimes silently fails or hangs indefinitely.
These errors are showing in the log:
From /var/log/nginx/error.log:
upstream timed out (110: Unknown error) while reading response header from upstream
From PHP-FPM logs:
[pool www] server reached pm.max_children setting (15), consider raising it
Steps I have tried to fix the problem:
• Increased memory_limit to 1024M and max_execution_time to 300
• Increased all FastCGI timeout values in Nginx to 300
• Tuned PHP-FPM settings:
pm.max_children = 30
pm.start_servers = 6
pm.min_spare_servers = 4
pm.max_spare_servers = 10
• Created new reports from scratch and narrowed filters ( although marketing prefers to have as much information as possible in these reports)
• Removed fields like “Subject” to get exports to complete successfully
Despite these changes, reports still time out or load very slowly when querying large datasets or certain fields. I’m wondering if there are known bottlenecks related to how Mautic handles reporting joins (e.g., with email subject or engagement data), or if there are best practices for optimizing report performance at scale.
Would love to hear how others are handling reporting at scale in Mautic 5.x, especially for high-volume email senders.
Apologies in advance if there’s already a solved thread or documentation on this that I missed, happy to be redirected if so.