1. After that tweet conversation with Mark Jaquith, I set up a live server with HHVM and are seeing similar performance advantages. I’m hoping to have my live site running it on it soon’ish.

  2. HHVM is awesome! Fortunately there are a lot of awesome projects in the PHP world lately, HHVM is definitely one of them! The team’s choice to go the FastCGI way makes it easy enough to switch to Nginx+HHVM from an Nginx+PHP-FPM setup (for example).
    One thing I’d really like to see in the future, although I’m almost sure it won’t happen (at least not in the foreseeable future): to run child processes with a different user and group, it would be great for security on shared environments.
    And thanks for mentioning my blog post / tutorial, Sarah! :)

    1. It’s not a different user or group, but I do have my test site setup to use PHP-FPM for my admin panel and HHVM for my front-end. I did this as I’m not sure how stable HHVM is just now, so I figured I may as well use the older slower PHP-FPM approach in the admin panel where performance isn’t as mission critical.

    2. Just like PHP-FPM you can run multiple HHVM processes as different users. It takes some manual work to set it up, but if you dig into /etc/init.d/hhvm you can see how the processes are initialized. Just create a new process that runs on a different port (just like with “pools” over TCP/IP on PHP-FPM).

      1. That’s true Bjørn, and it could be used as a workaround, however it takes around 500MB of RAM to start one process, even with a powerful dedicated server that would deplete resources quickly… :-/ And also based on my (somewhat limited) understanding of how HHVM works, this would actually be a lot less optimized because all processes would have to recreate the map of the translated code pieces instead of tapping the same database.

  3. I’m using OMGWTFBBQHHVMHHVVVM which is way better than this HHVVVM thing.

Comments are closed.