one of the key values at facebook is to move fast. for the past six years, we have been able to accomplish a lot thanks to rapid pace of development that php offers. as a programming language, php is simple. simple to learn, simple to write, simple to read, and simple to debug. we are able to get new engineers ramped up at facebook a lot faster with php than with other languages, which allows us to innovate faster.
today i'm excited to share the project a small team of amazing people and i have been working on for the past two years; hiphop for php. with hiphop we've reduced the cpu usage on our web servers on average by about fifty percent, depending on the page. less cpu means fewer servers, which means less overhead. this project has had a tremendous impact on facebook. we feel the web at large can benefit from hiphop, so we are releasing it as open source this evening in hope that it brings a new focus toward scaling large complex websites with php. while hiphop has shown us incredible results, it's certainly not complete and you should be comfortable with beta software before trying it out.
hiphop for php isn't technically a compiler itself. rather it is a source code transformer. hiphop programmatically transforms your php source code into highly optimized c++ and then uses g++ to compile it. hiphop executes the source code in a semantically equivalent manner and sacrifices some rarely used features ? such as eval() ? in exchange for improved performance. hiphop includes a code transformer, a reimplementation of php's runtime system, and a rewrite of many common php extensions to take advantage of these performance optimizations.
scaling php as a scripting language
php's roots are those of a scripting language, like perl, python, and ruby, all of which have major benefits in terms of programmer productivity and the ability to iterate quickly on products. this is compared to more traditional compiled languages like c++ and interpreted languages like java. on the other hand, scripting languages are known to generally be less efficient when it comes to cpu and memory usage. because of this, it's been challenging to scale facebook to over 400 billion php-based page views every month.
one common way to address these inefficiencies is to rewrite the more complex parts of your php application directly in c++ as php extensions. this largely transforms php into a glue language between your front end html and application logic in c++. from a technical perspective this works well, but drastically reduces the number of engineers who are able to work on your entire application. learning c++ is only the first step to writing php extensions, the second is understanding the zend apis. given that our engineering team is relatively small ? there are over one million users to every engineer ? we can't afford to make parts of our codebase less accessible than others.
scaling facebook is particularly challenging because almost every page view is a logged-in user with a customized experience. when you view your home page we need to look up all of your friends, query their most relevant updates (from a custom service we've built called multifeed), filter the results based on your privacy settings, then fill out the stories with comments, photos, likes, and all the rich data that people love about facebook. all of this in just under a second. hiphop allows us to write the logic that does the final page assembly in php and iterate it quickly while relying on custom back-end services in c++, erlang, java, or python to service the news feed, search, chat, and other core parts of the site.
since 2007 we've thought about a few different ways to solve these problems and have even tried implementing a few of them. the common suggestion is to just rewrite facebook in another language, but given the complexity and speed of development of the site this would take some time to accomplish. we've rewritten aspects of the zend engine ? php's internals ? and contributed those patches back into the php project, but ultimately haven't seen the sort of performance increases that are needed. hiphop's benefits are nearly transparent to our development speed.
hacking up hiphop
one night at a hackathon a few years ago (see prime time hack), i started my first piece of code transforming php into c++. the languages are fairly similar syntactically and c++ drastically outperforms php when it comes to both cpu and memory usage. even php itself is written in c. we knew that it was impossible to successfully rewrite an entire codebase of this size by hand, but wondered what would happen if we built a system to do it programmatically.
finding new ways to improve php performance isn't a new concept. at run time the zend engine turns your php source into opcodes which are then run through the zend virtual machine. open source projects such as apc and eaccelerator cache this output and are used by the majority of php powered websites. there's also zend server, a commercial product which makes php faster via opcode optimization and caching. instead, we were thinking about transforming php source directly into c++ which can then be turned into native machine code. even compiling php isn't a new idea, open source projects like roadsend and phc compile php to c, quercus compiles php to java, and phalanger compiles php to .net.
needless to say, it took longer than that single hackathon. eight months later, i had enough code to demonstrate it is indeed possible to run faster with compiled code. we quickly added iain proctor and minghui yang to the team to speed up the pace of the project. we spent the next ten months finishing up all the coding and the following six months testing on production servers. we are proud to say that at this point, we are serving over 90% of our web traffic using hiphop, all only six months after deployment.
how hiphop works
the main challenge of the project was bridging the gap between php and c++. php is a scripting language with dynamic, weak typing. c++ is a compiled language with static typing. while php allows you to write magical dynamic features, most php is relatively straightforward. it's more likely that you see if (...) {...} else {..} than it is to see function foo($x) { include $x; }. this is where we gain in performance. whenever possible our generated code uses static binding for functions and variables. we also use type inference to pick the most specific type possible for our variables and thus save memory.
the transformation process includes three main steps:
static analysis where we collect information on who declares what and dependencies,
type inference where we choose the most specific type between c++ scalars, string, array, classes, object, and variant, and
code generation which for the most part is a direct correspondence from php statements and expressions to c++ statements and expressions.
we have also developed hphpi, which is an experimental interpreter designed for development. when using hphpi you don't need to compile your php source code before running it. it's helped us catch bugs in hiphop itself and provides engineers a way to use hiphop without changing how they write php.
overall hiphop allows us to keep the best aspects of php while taking advantage of the performance benefits of c++. in total, we have written over 300,000 lines of code and more than 5,000 unit tests. all of this will be released this evening on github under the open source php license.
learn more this evening
this evening we're hosting a small group of developers to dive deeper into hiphop for php and will be streaming this tech talk live. check back here around 7:30pm pacific time if you'd like to watch.
as i'm sure there will be plenty of questions, starting this evening take a look at the hiphop wiki or join the hiphop developer mailing list. you'll also find us at fosdem, scale, php uk, confoo, tek x, and oscon over the next few months talking about hiphop for php. we're very excited to evolve hiphop into a thriving open source project along with all of you.
