[Piwik-hackers] Fatal error: Maximum execution time of XXX seconds exceeded

[Matthieu Aubry]

Patrick,
Piwik should not timeout. How it works
- first time you request data for a period (day, week, month, year) 
piwik will process the logs and compute the reports: it can take some 
time depending on your traffic (from 1 second to several minutes if you 
have hundreds of thousands of visits)
- then when you request data, it will only select the existing reports, 
which is very fast

Have you enabled always_archive_data = true in the configuration file?

Your traffic being small (1000 visits a day?) it should be very fast on 
any architecture..


Patrick Joyce wrote:
> Last night I began to get "Fatal error: Maximum execution time of 30
> seconds exceeded" errors when executing "Referers.getKeywords" for the
> period "last30".
>
> I first updated to the head of the trunk (r546) and this made no
> difference. I had installed and was previously running r521.
>
> I increased the maximum execution time to as high as 600 seconds to no
> avail. All the other API calls I do still work, and
> Referrers.getKeywords still works in under 60 seconds for periods of
> "last7", "last14", and "last21"
>
> "last28" times out at 600 seconds. Can the addition of 7 more days
> really result in a 10 fold increase in execution time?
>
> My install has about 20 different sites, 10 of which are active and is
> only processing about 100 visits a day.
>
> Any ideas on how to speed up execution?
>
> Thanks in advance for your help,
>
> Patrick Joyce
> _______________________________________________
> Piwik-hackers mailing list
> Piwik-hackers at piwik.org
> http://lists.piwik.org/cgi-bin/mailman/listinfo/piwik-hackers
>
>