rfc:max_execution_wall_time

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
rfc:max_execution_wall_time [2020/12/21 19:32] kocsismaterfc:max_execution_wall_time [2020/12/21 19:35] (current) kocsismate
Line 47: Line 47:
 ===== 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, similarly to what happens in case of "max_execution_time". 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, similarly to what happens when exceeding "max_execution_time". By default, the value of the new 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.
rfc/max_execution_wall_time.1608579133.txt.gz · Last modified: 2020/12/21 19:32 by kocsismate