You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
We're using Piwik with quite some success on many sites, even some high traffic ones. But after adding another high traffic site, we are running into a problem which I can best describe using a quote from "top":
As you can see, the archive.php task is eating up LOTS of memory using LOTS of CPU and taking LOTS of time to do its job. This is with Piwik 1.7.2-rc4. We already tried most if not all suggestions available on the forums and most about everywhere else - problem persists. If anyone is willing to look into this, help would be highly appreciated. Even SSH access to the system would be no problem.
System is a Debian Squeeze install with PHP 5.3.10 FPM and Apache 2.2.22 (worker) as frontend. Timeouts for FastCGI and FPM have been set to 10800 already to make up for the long run time but we're unable to complete at least one run of the today archive in that timeframe. The problem seems to be with the PHP task for the MySQL server is more or less idle during these runs.
The text was updated successfully, but these errors were encountered:
Thanks for the report. archive.php should be very cheap memory wise, memory is used by the API requests that are trying to archive the data. How many visits and pageviews do you have on your sites?
Thanks that was fast! Are the generated reports interesting?
Is it possible to email me matt@piwik the URL to access xhprof reports? I don't think teamviewer should be needed for that but let me know.
As I wrote in my email to you: since your schedule didn't allow for looking into this issue the client went back to using Adsense and removed Piwik from his setup completely. So the ticket can be closed for there is no more data to look at.
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
We're using Piwik with quite some success on many sites, even some high traffic ones. But after adding another high traffic site, we are running into a problem which I can best describe using a quote from "top":
As you can see, the archive.php task is eating up LOTS of memory using LOTS of CPU and taking LOTS of time to do its job. This is with Piwik 1.7.2-rc4. We already tried most if not all suggestions available on the forums and most about everywhere else - problem persists. If anyone is willing to look into this, help would be highly appreciated. Even SSH access to the system would be no problem.
System is a Debian Squeeze install with PHP 5.3.10 FPM and Apache 2.2.22 (worker) as frontend. Timeouts for FastCGI and FPM have been set to 10800 already to make up for the long run time but we're unable to complete at least one run of the today archive in that timeframe. The problem seems to be with the PHP task for the MySQL server is more or less idle during these runs.
The text was updated successfully, but these errors were encountered: