HipHop for PHP

HipHop for PHP
Stylized white "h" character on a blue background with a darker blue border on the character's edges
Developer(s) Facebook
Initial release February 2, 2010 (2010-02-02)[1]
Last release Replaced by HHVM[2][3] / 2013 (2013)
Development status Discontinued
Written in C++, C, PHP
License PHP License
Website github.com/facebook/hiphop-php

HipHop for PHP (HPHPc) is a discontinued PHP transpiler created by Facebook. By using HPHPc as a source-to-source compiler, PHP code is translated into C++, compiled into a binary and run as an executable, as opposed to the PHP's usual execution path of PHP code being transformed into opcodes and interpreted. HPHPc consists mainly of C++, C and PHP source code, and it is free and open-source software distributed under the PHP License.

The original motivation behind HipHop was to save resources on Facebook servers, given the large PHP codebase of facebook.com. As the development of HipHop progressed, it was realised that HipHop could substantially increase the speed of PHP applications in general. Increases in web page generation throughput by factors of up to six have been observed over the Zend PHP.[4][5][6][7][8] A stated goal of HPHPc was to provide a high level of compatibility for Zend PHP, where most Zend-based PHP programs run unmodified on HPHPc.[6] HPHPc was originally open sourced in early 2010.[1]

As an addition to HPHPc, Facebook engineers also created a "developer mode" of HipHop (interpreted version of a PHP execution engine, known as HPHPi) and the HipHop debugger (known as HPHPd). These additions allow developers to run PHP code through the same logic provided by HPHPc while making it possible to interactively debug PHP code by defining watches, breakpoints, etc. Running the code through HPHPi yields lower performance when compared to HPHPc, but the developer benefits were, at the time, worth having to maintain these two execution engines for production and development. HPHPi and HPHPd were also open sourced in 2010.[1]

By many accounts HPHPc fulfilled its goals, especially within Facebook as it allowed facebook.com to run much faster while using fewer resources. However, in early 2013 Facebook deprecated HPHPc in favor of the HipHop Virtual Machine (HHVM), which is a just-in-time (JIT) compilation-based execution engine for PHP, also developed by Facebook.[2][9] There were many reasons for this; one of them was HPHPc's flattened curve for further performance improvements. Also, HPHPc did not fully support the PHP language, including the create_function() and eval() constructs, and it involved a specific time- and resource-consuming deployment process that required a bigger than 1 GB binary to be compiled and distributed to many servers in short order. In addition, maintaining HPHPc and HPHPi in parallel (as they needed to be, for the consistency of production and development environments) was becoming cumbersome. Finally, HPHPc was not a drop-in replacement for Zend, requiring external customers to change their whole development and deployment processes to use HPHPc.[2]

See also

References

  1. 1 2 3 Haiping Zhao (2010-02-02). "HipHop for PHP: Move Fast". Facebook. Retrieved 2014-08-02.
  2. 1 2 3 Drew Paroski (2012-11-29). "Speeding up PHP-based development with HHVM". Facebook. Retrieved 2014-08-02.
  3. ↑ Paul Tarjan (2013-05-13). "Joining, Retirement, Testing, and Bankruptcy". hhvm.com. Retrieved 2014-08-02.
  4. ↑ "OOPSLA '12 Paper". Retrieved 2013-05-23.
  5. ↑ Guilherme Ottoni (2013-03-12). "The HipHop Compiler for PHP". OOPSLA 2012. Retrieved 2013-05-23.
  6. 1 2 "FOSDEM 2013 Interview". Retrieved 2013-05-23.
  7. ↑ "HipHop for PHP: Benchmark". Retrieved 2013-05-23.
  8. ↑ "Drupal 7: HipHop for PHP vs APC – benchmark". Retrieved 2013-05-23.
  9. ↑ "Announcement on GitHub removing HPHPc support". github.com. Facebook. 2013-02-19. Retrieved 2013-05-24.

External links

This article is issued from Wikipedia - version of the Thursday, January 28, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.