4 ms·
Given that in the conventional PHP interpreter, everything is executed from scratch on each request, I wonder how the JIT behaves here, especially since most PH
by apendleton 14y ago
Given that in the conventional PHP interpreter, everything is executed from scratch on each request, I wonder how the JIT behaves here, especially since most PHP programs live and die in less time than it seems to take the Pypy JIT to warm up. If/when a version with the web side of the stack is implemented, will JITed code survive across requests?
- fijal 14y agoin short - yes. there is nothing stopping the JIT code from surviving across requests, as long as you keep the process alive.
- ithkuil 14y agophp over fastcgi is a good example of how to reuse the same php process. I use http://php-fpm.org/ http://php-fpm.org/ and nginx and it's great.
- encoderer 14y agoThe issue is not dissimilar to using existing opcode caching.
- josephscott 14y agoAs mentioned, there is the opcode cache. I'm also thinking about FastCGI setups, where PHP is running the whole time, just waiting to execute code requests.