[Piwik-hackers] Fatal error: Maximum execution time of XXX seconds exceeded
Matthieu Aubry
matthieu.aubry at gmail.com
Wed Jul 23 01:16:52 CEST 2008
Thank you, doc updated.
Patrick Joyce wrote:
> Matthieu,
>
> Thanks for the clarification on how Piwik works. That was my understanding.
>
> I haven't modified the value of always_archive_data. It is set to false.
>
> When checking to make sure I understood the meaning of the setting I
> discovered this seemingly erroneous statement in
> http://dev.piwik.org/trac/wiki/Plugins/HowToWritePlugin (second bullet
> point of the testing section near the bottom)
>
> "You can define to archive data at each access to the statistic board
> - by default this is disabled for performance reason, but can be
> enabled in the config/global.ini.php by setting always_archive_data =
> false"
>
> I believe the sentence should end "... by setting always_archive_data = true".
>
> I agree I shouldn't be timing out with such a small data set. I'll
> keep looking for whatever the real problem is.
>
> Thanks again,
>
> Patrick Joyce
>
> On Thu, Jul 3, 2008 at 5:49 PM, Matthieu Aubry <matthieu.aubry at gmail.com> wrote:
>
>> 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
>>>
>>>
>>>
>> _______________________________________________
>> Piwik-hackers mailing list
>> Piwik-hackers at piwik.org
>> http://lists.piwik.org/cgi-bin/mailman/listinfo/piwik-hackers
>>
> _______________________________________________
> Piwik-hackers mailing list
> Piwik-hackers at piwik.org
> http://lists.piwik.org/cgi-bin/mailman/listinfo/piwik-hackers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.piwik.org/pipermail/piwik-hackers/attachments/20080723/54b21ae5/attachment-0001.htm
More information about the Piwik-hackers
mailing list