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
High CPU Usage, Widget Loading times out. #13262
Comments
When enabling the mysql slow query log it always fails on the following query:
I hit the same error when opening the Visitor-Log |
What were those 300K requests? How many visits/actions were there within last 24 hours? Maybe increase It seems some server configuration is not quite right. Real time query can be a bit "slow" but wouldn't consider "0.001631" slow for this query. |
Wait_timeout is already at 120s. |
Yes that's very likely the issue. |
I just brought up an visitor log of 10 users each visiting ~30 pages. It is not timing out, but is taking way too long. Doing the request, MariaDB hits 100% utilization. Any ideas on where to look for mistakes?
|
can you define way too long? No idea for where to look on mistakes. This should be fast. I recommend you get in touch with the Matomo support or ask in the forums for community help: https://forum.matomo.org/ We don't provide support for specific server issues in the issue tracker. The more details you provide the better. Eg database size, number of entries per |
I just benchmarked my Matomo 3.5.1 with Apache AB with 300,000 requests. Since then the widgets on the Dashbaord like "Visitors in real time" is not loading/timing out.
As soon as the request times out I get the error
WARNING: /var/www/html/piwik3.5.1/libs/Zend/Db/Statement/Pdo.php(228): Warning - Error while sending QUERY packet. PID=55294 - Matomo 3.5.1
on the page.I have added
wait_timeout=120
andmax_allowed_packet=1024M
and restarted the database, same error. Archiving is done via cronjob.It looks like one php-fpm process at 100% is blocking the whole web server (72core, 256GB RAM, 2TB SSD)
Any ideas or pointers?
The text was updated successfully, but these errors were encountered: