You might check out http://circus.readthedocs.org/en/latest/ instead of supervisord; you can restart managed processes on a schedule, and it also publishes events to zmq and statsd for integration with any other tooling you might want to use for health checks.
I just started a new Laravel project and decided to try hhvm. Unfortunately, on 3.8.0 it segfaults under load just serving the default Laravel page. It's really unfortunate since I'd love to give hhvm a shot.
That's cool I guess, but this article is more about setting up a load balancer than it is about HHVM. I was hoping for some juicy bit about it completely hosing up on some obscure PHP function.
Pragmatists, who know that "stable" and "unstable" branch are just tags, and what's important is the actual stability of the software in each as it relates to their use case.
People trading some known bugs for a whole heap of new ones, ones likely to change all the time? Doesn't sound like the smartest operations move.
Given they've gone and written stuff to automatically restart the processes under certain conditions anyway, might as well just catch the memory leak and restart, rather than gamble with "not for production use" software in production environments.
The build we're using was considered pretty safe and was performing better for us than 3.7.x - of course we aren't grabbing the new nightly constantly and plan to move to a "stable" branch soon :)
I'm not aware of a method to manage pools with systemd, also it requires processes to be daemonized which would make configuration a little messier. Also I'm simply more familiar with supervisord as systemd only recently became the default init system in debian.
> I'm not aware of a method to manage pools with systemd
I'm not sure what you mean by manage pools.
Maybe you're asking how to make multiple processes?
Check out unit templates, they're the ones with an '@' in them. see `man systemd.unit` for more info.
> also it requires processes to be daemonized which would make configuration a little messier.
