What Facebook’s HipHop means for PHP-based applications hosting
Today Facebook revealed what they have been working behind the scenes for a long time. In a nutshell, HipHop is aimed at improving PHP’s performance by converting PHP code to C++ and then compiling it with g++, thus allowing Facebook to keep up with their growth with fewer servers.
In theory, by running compiled code, users would get major gains in performance with the same hardware. This is specially true for applications and sites built using frameworks like Symfony, Zend Framework, Cakephp and others. But it also means that you will need to compile the PHP code and upload the result into a server that can understand and run it. In consequence, hosting that will support HipHop be limited.
We have some questions before hand that will get answered pretty soon. How does HipHop compare with running PHP with APC enabled? Since Facebook contributed a lot to APC, we are assuming that using HipHop should be an improvement. We also are very curious to see how it will fare with frameworks like Symfony and Zend Framework.
Here at ServerGrove, our core business is PHP hosting, and as you can imagine that we are very excited about this announcement. As we were one of the first companies to offer PHP 5.3 hosting, we will test HipHop to see what it offers for PHP hosting. Part of our mission is to squeeze every single CPU cycle to offer the best performance from our servers so our customers’ websites run as fast as possible. If HipHop is as good as it sounds, be sure that it will be added to our products offering, but not before making sure we can provide the top-level support that our customers deserve and get from us.
We look forward to hearing your predictions on HipHop. How will symfony and Zend Framework fit in the schema of things? How will this affect our workflow? If HipHop is as good as it sounds, what will be the ultimate hosting product to go with it? Check back soon, as our tests materialize we will post them here.


Pablo, thanks for being on top of this already. You are echoing the same questions I’ve raised, and the same optimism based on Facebook’s past experience with APC and other existing alternatives. The Facebook blog post was quite careful to point out all of the existing efforts to speed up PHP.
At the HipHop presentation last night, Facebook said that HipHop is 50% faster with the same amount of traffic on their web tier, and 30% faster with double the traffic on their API tier. Those percentages are based on comparing HipHop to PHP with APC, so apparently it’s way faster than even opcode caching.
Most of my questions surround the viability of code conversion. It’s long been history that this kind of technology is bug-prone at best.
It just sounds like you’re going to generate lots of problems that exist only in the conversion later, and that will never be found when the developer has to go back and debug in pure PHP.
Nevermind that Hip Hop only supports “several popular extensions”… which leaves anyone who uses one of the “unpopular” extensions out in the cold.
Great information. Thanks for introducing HipHop. I was looking for this since few days… Onthenetoffice