4 ms·

Given how much PHP is used, having a JIT will probably save a meaningful amount of electricity

by piinbinary 7y ago

agumonkey 7y ago
I'm not sure if I'm inventing things but I think there was a report when facebook introduced hiphop compiler.
- tpetry 7y ago
  Yes hiphop compiler was very fast when they started but shortly after normal php was faster than the hiphop compiler. So the hiphop compiler transformed into hhvm which was php with some really nice additions. But at some point the language inventions got more and more in conflict with the increments in the php language so they dropped php support and its now only using its own language which is a very improved version of php
- deleted 7y ago
  [deleted]
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 ago
  It'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 ago
    Also check for memory leaks while you are at it.
- detaro 7y ago
  It 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 ago
  I 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 ago
    In 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).
kyriakos 7y ago
The main benefit will be for long running php processes rather than stateless web requests. It does open php as an option for other applications which are currently being implemented with nodejs and python.
- ahupp 7y ago
  Typically the JITted code is saved between requests, since it's stateless. This is how HHVM works at least.
gcpwnd 7y ago
The JIT won't be a game changer, at least initially.
thdrdt 7y ago
PHP7 already dropped the load on a lot of servers. It was amazing to see that systems like WordPress became twice! as fast by just switching PHP version.
- pmlnr 7y ago
  Don't you worry: WordPress will slow itself down soon enough, at least on the user side with React and Gutenberg.

Given how much PHP is used, having a JIT will probably save a meaningful amount of electricity

agumonkey 7y ago

I'm not sure if I'm inventing things but I think there was a report when facebook introduced hiphop compiler.

tpetry 7y ago
Yes hiphop compiler was very fast when they started but shortly after normal php was faster than the hiphop compiler. So the hiphop compiler transformed into hhvm which was php with some really nice additions. But at some point the language inventions got more and more in conflict with the increments in the php language so they dropped php support and its now only using its own language which is a very improved version of php
deleted 7y ago
[deleted]

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 ago
It'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 ago
  Also check for memory leaks while you are at it.
detaro 7y ago
It 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 ago
I 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 ago
  In 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).

kyriakos 7y ago

The main benefit will be for long running php processes rather than stateless web requests. It does open php as an option for other applications which are currently being implemented with nodejs and python.

ahupp 7y ago
Typically the JITted code is saved between requests, since it's stateless. This is how HHVM works at least.

gcpwnd 7y ago

The JIT won't be a game changer, at least initially.

thdrdt 7y ago

PHP7 already dropped the load on a lot of servers. It was amazing to see that systems like WordPress became twice! as fast by just switching PHP version.

pmlnr 7y ago
Don't you worry: WordPress will slow itself down soon enough, at least on the user side with React and Gutenberg.