The HipHop Virtual Machine

[mrich]

Sounds like they are some experienced software engineers:

>The first 90% of the hhvm project is done; now we're on to the second 90% as we make it really shine.

[k_bx]

Really experienced mention the third 90% http://morepypy.blogspot.com/2011/11/gothenburg-sprint-repor... (search 90%)

[josefresco]

Going to use that line next time a client asks me "how close we are to launch".

[keeran]

Couldn't help but chuckle at the code example

  return $hit

[draegtun]

Yes its amazing how easy it sneaks in! Was looking at a gist of mine recently (https://gist.github.com/1222875) and it suddenly jumped out at me!

  my $hits = ...

  for my $hit (@$hits) {
      my $user = $hit->{_source};
      ...
  }

:)

[beagle3]

The state of the art in JITs is LuaJIT2, despite almost no fanfare (and lots of fanfare by other JIT projects). I haven't had a look at hhvm yet, but if anyone wants a cool project, make hiphop emit Lua instead of C++, and run it under LuaJIT2.

LuaJIT2 really is magic, and Mike Pall is a humble but talented magician.

[enduser]

This is a good reminder not to build anything other than a prototype in a language that you're going to regret later.

[scotty79]

If they started with Python (or anything else) they would have ended up in the same place. They would end up writing their own compiler and VM because they want and they can. It's actually amazing that they didn't extend the language itself yet.

[leftnode]

Facebook also has some unique traffic problems that almost no other startup is going to experience.

[tyree732]

I can't imagine that Facebook regretted PHP until it was too late for them to do anything about it.

[cbo]

It's impossible to know what you'll need in the future. No one should be wasting too much time trying to figure it out.

How could Zuckerberg -- or anyone, for that matter -- have predicted the kind of rampant success Facebook has had? Who thought in 2005 that Facebook would become the largest photo sharing site on the web? Or that they would need to handle almost 140 million unique visitors per month?

If the largest problem of your business is your application stack, you are in a very good place. Most businesses have much larger problems like, say, cashflow.

[ericmoritz]

Excuse my ignorance of LLVM but couldn't someone build a PHP LLVM JIT compiler and stand of the shoulders of that project?

I am sure I am trivializing the effort that it takes to make JIT for PHP.

[rayiner]

LLVM isn't the worlds greatest target for a dynamic language, as Rubinius and Unladen Swallow found out. It does a lot of low level optimization, but a basic prerequisite to that is being able to do some sort of optimistic type-based optimizations, and LLVM has no infrastructure for that.

It looks like HipHopVM uses tracing which is probably a better way to go.

[aurelianito]

This is the kind of things that make me want to work in a company like Facebook.

[cpeterso]

This is the kind of things that make me not want to work in a company like Facebook.

[js4all]

The hhvm is some nice piece of software, but it also takes many resources. This will always remind me to be very careful when making a design decision, like what language to use for project.

[nodesocket]

We are looking into running our API on HipHop, but not until the load justifies the effort to migrate. Currently running on lighttpd with PHP-FPM.

[lansing]

Looks like an impressive, cool project.

The justification for why it matters seems a bit "off" to me:

  For perspective on why this matters, consider that many Facebook engineers 
  spend their days developing PHP code in an endless edit-reload-debug cycle. 
  The difference between 8-second and 5-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.

Big leap of intuition follows, bear with me:

Clearly there are some very talented engineers working at Facebook, as evident by this project. On the other hand, apparently a large number of Facebook engineers are spending all their time in a run-debug cycle, trying to "make this darn thing work," and the engineers with talent are being used to incrementally improve the mediocre coders' lackluster productivity.

Guys, if three seconds in compile overhead makes such a difference in your productivity, maybe you should think for a few seconds about code correctness before you hit the compile button.

[kmavm]

All engineers, those who work on HHVM like me included, spend their lives in a run-debug cycle trying to "make this darned thing work," whether "this darned thing" is a language runtime or the new photo uploader. The tighter you can make that loop, the more productive the engineer is, because she has less time to keep all the items she's mentally juggling pinned in volatile short-term memory.

[monopede]

Note that in many dynamic languages (and I think that includes PHP), syntax checking is done right before you try to run it, and type checking is performed at runtime. When you're programming in a Java IDE, these kinds of errors (and related ones, like typos in variable names, etc.) all get resolved while you're typing. In PHP or JavaScript you only find out once you run the program, so saving 3 seconds can be a huge win.

Of course, you can do static analysis to some degree which would cut down that time even further, but you may also get false alerts or miss some issues.

[spitfire]

"The x64 machine code that the translator generates consumes approximately ten times as much memory as the corresponding HHBC. CPU instruction cache misses are a limiting factor for the large PHP applications that Facebook runs, so a hybrid between interpretation and translation may outperform pure translation."

This tells me that the engineers on the hhvm project are at least smarter than the engineers on the Java language.

[rat87]

what did the java engineers get wrong? Hotspot performs fast interpretations then compiles after multiple run of a piece of code.