rfc:max_execution_wall_time
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| rfc:max_execution_wall_time [2020/12/13 00:14] – kocsismate | rfc:max_execution_wall_time [2020/12/13 00:18] – kocsismate |
|---|
| ===== Proposal ===== | ===== Proposal ===== |
| |
| This RFC proposes to add a ''max_execution_wall_time'' ini setting. If a script runs longer than the value of ''max_execution_wall_time'' measured in seconds according to wall-clock (or real) time, a fatal error is raised. By default, the value of the ini setting is ''0'', which means that the allowed script duration is unlimited. | This RFC proposes to add a ''max_execution_wall_time'' ini setting. If a script runs longer than the value of ''max_execution_wall_time'', measured in seconds according to wall-clock (or real) time, a fatal error is raised. By default, the value of the ini setting is ''0'', which means that the allowed script duration is unlimited. |
| |
| A limitation of the implementation is that the timeout takes into effect on a best-effort basis, meaning that the fatal error is triggered only after the call exceeding the time limit is finished. This is in line with the current timeout behavior, and the RFC considers this as an acceptable limitation. | A limitation of the implementation is that the timeout takes into effect on a best-effort basis, meaning that the fatal error is triggered only after the call exceeding the time limit is finished. This is in line with the current timeout behavior, and the RFC considers this as an acceptable limitation. |
| |
| Furthermore, there is a question in case of platforms which already measure ''max_execution_time'' based on wall-clock time. The most notable of such systems is definitely Windows, but IBM PASE and Cygwin are also affected, since they both only support real-time timers. The position of this RFC is that ''max_execution_wall_time'' should act as an "alias" of ''max_execution_wall_time'' on these platforms, so changing any of the settings in question would affect the same timer. | Furthermore, there is a question in case of platforms which already measure ''max_execution_time'' based on wall-clock time. The most notable of such systems is definitely Windows, but IBM PASE and Cygwin are also affected, since they both only support real-time timers. The position of this RFC is that ''max_execution_wall_time'' should act as an "alias" of ''max_execution_time'' on these platforms, so any changes to the settings in question would affect the same timer. |
| |
| Adding a ''set_time_limit()'' counterpart is out of scope of the current RFC. | Adding a ''set_time_limit()'' counterpart is out of scope of the current RFC. |
rfc/max_execution_wall_time.txt · Last modified: 2020/12/21 19:35 by kocsismate