Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111977
MIME-Version: 1.0
References: <ME2P282MB02272021544EFDBE6BF44A23F2300@ME2P282MB0227.AUSP282.PROD.OUTLOOK.COM>
 <940131FA-19B3-406C-8982-0AD276FD1879@gmail.com> <CAF+90c8y6dpqMg8s+X-ndQwp52CDL7Q9oHL_DwDQ1OS-k1GR9w@mail.gmail.com>
 <142da816-f3bf-2f05-6147-ccd2117e1dfd@gmail.com>
In-Reply-To: <142da816-f3bf-2f05-6147-ccd2117e1dfd@gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Thu, 1 Oct 2020 10:32:11 -0600
Message-ID: <CAAKU0umtQNko3PQGQ-V45wWk-_PC7NNcD9rKiNC8pWDuS9FxMg@mail.gmail.com>
To: Dik Takken <dik.takken@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Rowan Tommins <rowan.collins@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] RFC: execution opcode file without php source code file
From: internals@lists.php.net ("Levi Morrison via internals")

On Thu, Oct 1, 2020 at 9:14 AM Dik Takken <dik.takken@gmail.com> wrote:
>
> On 01-10-2020 14:30, Nikita Popov wrote:
> > It would be good to know what the actual use-case for this is. If the goal
> > here is to distribute pre-compiled PHP code without the source code, then
> > this is not going to work without making the opcode format stable (which, I
> > think, is pretty unlikely.) If the goal is improving cold startup
> > performance, then I wonder what the benefit over the existing file cache is.
>
> The only use case I see is to package commercial closed source
> applications as Docker containers. That allows the packager to ship the
> compiled code along with the exact PHP version and configuration that
> can run it reliably.
>
> Regards,
> Dik Takken

Note that for PHP 8.0 we made the system ID change even more than it
used to because doing so fixes sigsegvs when switching what extensions
are loaded (common when trialing an APM product, or loading and
unloading xdebug) when file cache is used. This means that it is even
more important to have sources than in the past, and necessarily so
because of real segmentation faults.

So I second Nikita's opinion: this is not going to work well without
stabilizing the opcode format. This may be possible, but it would be a
lot of work; it's not happening soon. If you do it anyway be prepared
for plenty of crash complaints.