This page is a translated version of the page HHVM and the translation is 34% complete.

HHVMはPHPインタープリターツール(より厳密にはランタイムにPHP bytecodeをネーティブの指示に変換する仮想マシンのこと)で、2014年にウィキメディアのサーバに実装されると右記の操作でページ読み込みに要する時間が短縮されました。ログイン利用者のページ閲読、またログイン状態を問わずページの編集を保存するとき。

See HHVM/About for a shorter description, and the December 2014 blog post "How we made editing Wikipedia twice as fast" for more background on HHVM, its benefits, and a look back on the deployment work.
In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.[1] After discussion[2] WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See タスク T176209 and タスク T192166.


HHVM is a new way for websites to run MediaWiki (written in PHP). It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT). HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.




  • βクラスタへの実装(他の準備と並行して作業)  完了
  • 2014年7月21日の週:製作クラスタのジョブランナー数件に実装  完了
  • アプリケーションサーバに実装  完了
  • Varnishモジュールの実装を介してアプリケーションサーバ群に部分的に実装を可能にする  完了
  • 限定的にごく少数のアプリケーションサーバに実装  完了
  • 段階的にアプリケーションサーバ群への実装を進めてHHVMの使用を大多数のサーバに広げる  完了
  • その他のサービスに実装  完了


Phabricator: 未完のタスク全タスク


It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.[3][4] As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular. Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.[5] Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.

Facebook, as a big user of PHP, has recognized this problem, and invested heavily[6] in a solution: HHVM, a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages. We're quite confident that this will result in big performance improvements on our sites as well.

HipHop がエンドユーザに与える影響は?

MediaWiki is written in PHP, a language that is interpreted at run-time. The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as Varnish, which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed. These caches only serve users that are not logged in.[7] Actions which are not affected by the cache, and therefore are affected by the run time of PHP code, include:

  • Any page you view while logged in.
  • Saving pages that you've edited, whether you are logged in or not.

Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously.

HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter (Zend). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites.


In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend. This will be on a totally opt-in basis which can be disabled at any time. This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases. It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.

For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to. However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.



  1. Max Wang, "The future of HHVM"
  2. "HHVM vs. Zend divergence" on wikitech-l
  3. "Bing and Google Agree: Slow Pages Lose Users" - Brady Forrest - O'Reilly Radar
  4. Greg Linden's blog: "Marissa Mayer at Web 2.0" - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.
  5. "Wallflower at the Web Party", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."
  7. By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page. This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.