Re: Support for writing and executing compiled opcode Stephen Coakley <me@stephencoakley.com>
| From: | Jefferson Gonzalez | Date: | Mon, 16 Nov 2015 20:13:47 +0000 |
| Subject: | Re: Support for writing and executing compiled opcode Stephen Coakley <me@stephencoakley.com> | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals php.internals |
| Request: | Send a blank email to internals+get-89241@lists.php.net to get a copy of this message | ||
On 11/14/2015 08:03 PM, Rasmus Lerdorf wrote:
Beyond that I can't picture what possible use this could be.I also think that the ability to have a .phpc and .php side by side would be nice, but not for hiding the source code. It would be useful especially for php-cgi and secondary for php-cli. In php-cgi case theres people who still host multiple sites on a single server and use the php-cgi method because it doesn't requires to have an always running instance like with php-fpm. Lets say you are hosting 100 sites on a single server, imho it would be less resourceful to run php-cgi processes on demand than having more than 100 fpm processes idling for requests. So in this scenario, having the flexibility to load byte code for php-cgi process would be a nice performance boost.