3 ms·
that page seems to state that it only works in the context of a single request unless you've got CPU bound PHP code... it seems like a complete waste of effort
by blibble 7y ago
that page seems to state that it only works in the context of a single request
unless you've got CPU bound PHP code... it seems like a complete waste of effort
- kyriakos 7y agoIt's a way to promote php for other type of applications. Check swoole and reactphp, they will be benefiting the most.
- deleted 7y ago[deleted]
- softwarelimits 7y agoAlso check for memory leaks while you are at it.
- detaro 7y agoIt isn't limited to a single request, it's merely pointing out that typical web request handling has more limited potential for performance gains from it.
- geekpowa 7y agoI am guessing blog author has got some things wrong here. I would expect JIT will be useful in a fastcgi setup. Edit: to clarify, PHP processes in fastcgi persist across multiple web requests. So seems reasonable to me that a JIT would do useful work here. The JIT could even run while the PHP process in a fastcgi pool is idle waiting for next job.
- monoideism 7y agoIn Facebook's HHVM, PHP has had a JITed interpreter for well over 5 years that people have used in production for great gains. However, most people have moved back to reference PHP 7+ and I believe HHVM had even stopped supporting PHP (it's main use was as an interpreter for & three closely related Hack language).