Page MenuHomePhabricator

/maniphest/report/project/ : Maximum execution time of 10 seconds exceeded
Open, LowPublic



Maximum execution time of 10 seconds exceeded


┻━┻ ︵ ¯\_(ツ)_/¯ ︵ ┻━┻

Related Objects

Event Timeline

Nemo_bis created this task.Jan 31 2016, 9:52 PM
Nemo_bis updated the task description. (Show Details)
Nemo_bis raised the priority of this task from to Needs Triage.
Nemo_bis added a project: Phabricator.
Restricted Application added subscribers: StudiesWorld, Luke081515, scfc, Aklapper. · View Herald TranscriptJan 31 2016, 9:52 PM

Not sure what to say about that. The queries on that page are expensive, sometimes they will probably time out. It's sort of to be expected.

Aklapper triaged this task as Low priority.Feb 9 2016, 10:57 PM
greg added a subscriber: greg.

I can't get it to load at all today, that doesn't seem right, right?

greg added a comment.Apr 1 2016, 4:57 PM

I can't get it to load at all today, that doesn't seem right, right?

Ok ok, it took 6 tries, but I got it to load now. :)

Paladox added a subscriber: Paladox.EditedSep 6 2016, 11:32 AM

I guess we should file this upstream to see if any performance improvements can be done to it?

Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptSep 6 2016, 11:32 AM

We should debug a bit ourselves first before potentially contacting upstream. for anyone interested.

We have php's maximum execution time set much lower than the default. I don't think that it would fail with the default 10 seconds.

@mmodell , i thought it was already 10 seconds?

What about increasing it to 15 or 20 seconds?

Change 335714 had a related patch set uploaded (by Paladox):
Up max_execution to 20 from 10 in phabricator/php.ini.erb

Change 335714 abandoned by Paladox:
Up max_execution to 15 from 10 in phabricator/php.ini.erb

Aklapper added a comment.EditedMar 24 2017, 3:34 PM seems to work for me again. Not sure why.
Other queries such as still sometimes do not work, sometimes they do.

mmodell added a comment.EditedMar 27 2017, 10:42 AM

It's because the report is very computationally expensive to generate, so it can only complete within the time limit when all of the circumstances align perfectly. This only works in the exceedingly rare event such as when the moon is full while simultaneously there is unusually little activity on all of phabricator's servers (web app + database).

This still appears to be an issue.


Maximum execution time of 10 seconds exceeded


┻━┻ ︵ ¯\_(ツ)_/¯ ︵ ┻━┻

Patch was abandoned.

Is it at least possible to catch the exception and print that it's a pretty normal error, with a link to this task ?

Aklapper added a comment.EditedDec 2 2017, 11:20 PM

Which problem would that solve which outweighs the costs for maintaining some custom patch to link to some custom bug report?

Change 410631 had a related patch set (by Paladox) published:
[operations/puppet@production] Phabricator: Raise php max_execution_time to 15

Paladox added a comment.EditedFeb 15 2018, 2:25 AM

I've raised the timeout here ^^ hoping that will at least improve it some what, but this does seem very slow.

Timeout says it is on

@Paladox: Please read Chad's comment from 2017-02-06 on again.
Ignoring feedback is not a good use of anybody else's time.

@Aklapper sorry, i forgot about that, i cannot remember everything.

Change 410631 abandoned by Paladox:
Phabricator: Raise php max_execution_time to 15

Aklapper moved this task from To Triage to Misc on the Phabricator board.Aug 29 2018, 8:18 PM
Paladox added a subscriber: MGChecker.

We increased the max_execution_time to 30s in for php-fpm.

So once we switch to stretch we can switch on php-fpm and then it should work.

greg removed a subscriber: greg.Thu, Apr 11, 9:49 PM