Facebook 'HipHop VM' juices PHP speed pill
Aim to bust engineers out of edit-reload-debug dungeon
Facebook hopes to shave seconds off of its PHP web pages loads and juice its servers' performance with an execution engine for the C++ code transformer it cooked up last year.
The web giant's engineers have unveiled something called HipHop Virtual Machine (hhvm) for the HipHop for PHP product already being used in software development by Facebook.
The plan is to eventually use hhvm for the execution of all PHP code on Facebook, according to hhvm project contributor Jason Evans here.
It's not clear when the change over will take place, however, as Evans reckons that the translator still needs to be stabilized and there's need for creation of an on-disk byte code format that will help reduce start-up times and store global static analysis results.
Facebook's come up with hhvm to further the work from last year on HipHop for PHP. This was conceived to speed-up Facebook page-load times and to help squeeze more compute performance from its army of 10,000 servers.
HipHop for PHP takes PHP - a flexible, dynamic language favored for the web - and converts it into C++, a statically typed language that's the world's third most popular programming language; it remains popular in part, because compiled C++ executes fast compared to interpreted languages.
The problem for Facebook was that HipHop for PHP compiled PHP statically, a fact Facebook tried to sidestep with the creation of an interpreter called hphpi.
However, Evans reckons Facebook's found hphpi takes a lot of effort to maintain.
Based on early numbers, the hhvm byte code interpreter is approximately 1.6x faster for a set of real-world Facebook-specific benchmarks than the interpreter. The translator is approximately 0.6X as fast as hphpc but not quite as fast as hphpc-compiled binaries.
"For perspective on why this matters, consider that many Facebook engineers spend their days developing PHP code in an endless edit-reload-debug cycles," Evans said.
"The difference between eight-second and five-second reloads due to switching from hphpi to the hhvm interpreter makes a big difference to productivity, and this improvement will be even more dramatic once we enable the translator."
Evans reckoned his team expects to rapidly close the performance gap between hhvm and hphpc-compiled binaries during the coming months as the dynamic translator stabilizes and matures.
"In fact, we predict that hhvm will eventually outperform statically compiled binaries in Facebook's production environment, in part because we are already sharing enough infrastructure with the static compiler that we will soon be able to leverage static analysis results during tracelet creation," he said. ®
Optimisation like that would be seriously expensive for development time though. Managing the complexity of and testing process oriented code is not fun.
If the tool is only 1.6x faster at executing compiled byte code, it is just another interpreting language concept like Java, not a true compiler for transforming code to C++. By replacing all object oriented programming in their PHP source code with simple plain old function calls, they would get about the same 1.6x performance increase.