Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89212 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16180 invoked from network); 14 Nov 2015 02:32:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Nov 2015 02:32:56 -0000 X-Host-Fingerprint: 68.118.157.39 68-118-157-39.dhcp.mdsn.wi.charter.com Received: from [68.118.157.39] ([68.118.157.39:26789] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/63-62946-75D96465 for ; Fri, 13 Nov 2015 21:32:55 -0500 Message-ID: <54.63.62946.75D96465@pb1.pair.com> To: internals@lists.php.net References: <12.A1.62946.CB756465@pb1.pair.com> <564659DF.5070904@php.net> <77.62.62946.F6D56465@pb1.pair.com> <80ED4CA4-1548-48B5-A94B-B3FA1377C755@lerdorf.com> Date: Fri, 13 Nov 2015 20:32:52 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <80ED4CA4-1548-48B5-A94B-B3FA1377C755@lerdorf.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 68.118.157.39 Subject: Re: [PHP-DEV] Support for writing and executing compiled opcode From: me@stephencoakley.com (Stephen Coakley) On 11/13/2015 05:46 PM, Rasmus Lerdorf wrote: > On Nov 13, 2015, at 17:00, Stephen Coakley wrote: >> >>> On 11/13/2015 03:45 PM, Sebastian Bergmann wrote: >>>> On 11/13/2015 04:35 PM, Stephen Coakley wrote: >>>> This is quite similar to Python's ability to execute Python scripts >>>> compiled to bytecode as *.pyc files. The feature has seen great >>>> success in >>>> Python, mostly for distributing releases of software or deploying to a >>>> server. >>> >>> Correct me if I'm wrong, but this should already be possible with OpCache >>> and its filesystem backend in PHP 7.0. >>> >>> See http://talks.php.net/froscon15#/php7pcache1 and following for >>> details. >> >> That's great! That's about halfway toward what I'm looking for. That means that the engine is likely already capable of doing these things -- the next step is to be able to execute any given .php.bin file like in that talk. The idea would be to be able to bypass the caching mentality by executing an already compiled file, instead of checking if the original .php file has a corresponding bin file in the cache > > You could simply deploy both the .php and the .bin files to achieve this today. > > -Rasmus > Would the bin files not have to be placed in the special OPcache file store location though? That seems sub-optimal. I'm glad it's already possible though. Thanks for the tip. -- Stephen