The HHVM team, along with our wonderful open source contributors, is constantly trying to improve the runtime. We know, however, that there is work to do to run the world’s PHP code reliably and consistently.
Every 6 months or so, the HHVM team goes into lockdown. Lockdown is a Facebook tradition where a team picks a few concentrated areas and pushes hard on them. The team is huddled together. No meetings. Specific task focused. Shaving is discouraged.
The HHVM team’s latest Lockdown started on Monday. It is a 3-week effort focused entirely on two things: performance and parity.
The first graph is our performance graph. The second graph is our parity graph, and the percentages are unit tests passing per framework. Simply put, by the end of the three weeks, we want to have had each graph move up and to the right. (Note: The dip you see in the parity graph is our unit test script misbehaving. The script is being continuously modified to make our testing better and more valuable).
The stickies below are an example of the individual tasks to get us there. We have prioritized them by impact (e.g., number of unit tests that will pass upon completion of the task) and length (how many days the task will take to complete). If these stickies are moved to the “Done” column, the graphs should respond favorably.
The HHVM team really cares about maintaining a high quality runtime for PHP. At the end of the three weeks, the no shaving mantra having fully taken hold, we are hoping you see a much better HHVM in terms of being able to accurately run a broader array of PHP code, very fast. Stay tuned for the results of this lockdown.