Normally I would set_time_limit(0) for a specific type of request, and let others be limited. However, set_time_limit() does not work under Octane (Swoole) and octane.max_execution_time is enforced on all processes. It's done by the server and set when the server starts.
I'd like to implement this possibility, but I'd need some help with that. I've found EnsureRequestsDontExceedMaxExecutionTime that uses timerTable created in bin/createSwooleTimerTable.php. So, I suppose I could modify (move forward) the 'time' property in that table or introduce another column with max_execution_time. Would that work?
How do I get 'worker_pid' from outside of Octane?
How do I access the table from outside of Octane?
How do I access the current worker?
Would you be interested in a public API for that? Where would I put it?
Thank you. Right now we don't have plans to contribute to this feature ourselves. Should you need help with trying to build a PR for this it's best that you try a support channel:
Normally I would
set_time_limit(0)
for a specific type of request, and let others be limited. However,set_time_limit()
does not work under Octane (Swoole) andoctane.max_execution_time
is enforced on all processes. It's done by the server and set when the server starts.I'd like to implement this possibility, but I'd need some help with that. I've found
EnsureRequestsDontExceedMaxExecutionTime
that usestimerTable
created inbin/createSwooleTimerTable.php
. So, I suppose I could modify (move forward) the 'time' property in that table or introduce another column with max_execution_time. Would that work?