Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112783
MIME-Version: 1.0
References: <CAH5C8xW981Fn91HsHmZfbLseXwSyOtM1X5u1zsAL4ofXhka=nw@mail.gmail.com>
In-Reply-To: <CAH5C8xW981Fn91HsHmZfbLseXwSyOtM1X5u1zsAL4ofXhka=nw@mail.gmail.com>
Date: Wed, 6 Jan 2021 17:26:13 +0100
Message-ID: <CAF+90c-KZwhkSjrKqKNtLWtMZuhFSQreJpAbZaKApOwmdTf7mQ@mail.gmail.com>
To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= <kocsismate90@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000016a1d105b83dc94a"
Subject: Re: [PHP-DEV] [RFC] [Discussion] Measuring maximum execution time
 based on wall-time
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000016a1d105b83dc94a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 13, 2020 at 1:25 AM M=C3=A1t=C3=A9 Kocsis <kocsismate90@gmail.c=
om> wrote:

> Hi Everyone,
>
> Thanks for all the insightful feedbacks so far, I went ahead, and wrote a
> proper
> RFC: https://wiki.php.net/rfc/max_execution_wall_time
>
> Regards:
> M=C3=A1t=C3=A9
>

Something potentially worth pointing out (and assuming I'm inferring the
correct behavior here): If max_execution_wall_time is exceeded during an
internal function call (which seems quite likely, as that's where there is
the most potential for something to hang) and the function does not return
within hard_timeout seconds, then the a process abort will be triggered.
The hard_timeout is 2s by default. If any of the individual call timeouts
are >=3D 2s, then it's not unlikely that this situation occurs.

Regards,
Nikita

--00000000000016a1d105b83dc94a--