3 ms·

Welp, so much for “PHP has JIT too.”

• singlow 8y ago
  The official PHP JIT branch is nearing release which would have made HHVM less relevant. I think it is expected to be in 8.0, whenever that hits.
  • mgkimsal 8y ago
    My understanding is that a PHP 8, as it stands right now, is looking like Nov 2020.
• ehnto 8y ago
  They increased performance of the language enough that it caught up to HHVM. PHP7 is wildly faster than previous PHP versions. In other words, HHVMs value proposition of speed is no longer as relevant. PHP is still working on a JIT implementation but I honestly don't think it's that important for now.
  • postalrat 8y ago
    In my experience HHVM is still quite a bit faster once it gets going.
  • kyriakos 8y ago
    Due to the short lived nature of PHP requests JIT compilation wont be as effective as one would expect. Still though since php 7,every point release saw a measurable performance improvement.
• thawkins 8y ago
  PHP 7 has Zend OPtimizer built in, basically a caching bytecode compiler. Previous versions used to use the APC extension to serve the same purpose.
  • bpicolo 8y ago
    That's distinct from JIT - it's just a way to prevent having to re-parse/compile to byte code every single request to your site (no other language has this issue)
    • ars 8y ago
      > no other language has this issue Because no other language is as easy to deploy. With PHP you edit the PHP file, and that's it. It's deployed. No clearing cache, no compiling, packaging, nothing. It's one of the major factors in how good of a language it is. If it's needs this optimization as a result of that, it's completely worth it, and other languages should copy that.
      • bpicolo 8y ago
        > Because no other language is as easy to deploy Nah, it's because PHP isn't an actively running process. The overhead of starting a process isn't what it used to be in shared web infra world before. It's cheap to spin up a small VM now. And there are other similar constructs, e.g. FaaS