This makes sense.
From: jakub@gmail.com on behalf of Jakub Zelenka
Sent: Friday, April 20, 2018 1:04:01 PM
To: Dmitry Stogov
Cc: PHP internals list
Subject: Re: FPM preloading of PHP files
Hi Dmitry,
On Fri, Apr 20, 2018 at 8:54 AM, Dmitry Stogov
mailto:
Hi Dmitry,
On Fri, Apr 20, 2018 at 8:54 AM, Dmitry Stogov wrote:
> Hi Jakub,
>
>
> I thought about pre-loading explicitly specified files (or directories) on
> PHP startup, before forking worker processes.
>
> As result all pre-loadd files should be available to all workers. Of
> course the shou
Hi Jakub,
I thought about pre-loading explicitly specified files (or directories) on PHP
startup, before forking worker processes.
As result all pre-loadd files should be available to all workers. Of course the
should be kept in immutable form.
Thanks. Dmitry.
__
Hi Dmitry
On Tue, Apr 17, 2018 at 5:44 PM, Dmitry Stogov wrote:
> Hi Jakub,
>
>
> I though not only about FPM, but a technology for any SAPI.
>
> Pre-loaded classes and functions might be kept in CG() tables, in the same
> way as "internal" ones.
>
> EG() constants and variables may be re-create
Hi Jakub,
I though not only about FPM, but a technology for any SAPI.
Pre-loaded classes and functions might be kept in CG() tables, in the same way
as "internal" ones.
EG() constants and variables may be re-created at start of request, executing
pre-loaded PHP code.
Few years ago, I develop
