[deanotron]

HHVM was needed at Facebook because it's a dynamic app with rapidly changing content.

WordPress sites are typically static content that are perfectly fit for static caching with a CDN - it really shouldn't matter how many milliseconds you are able to save on the server if your site is only being hit once every two hours from the CDN.

The 8 million caching plugins are unnecessary when you can just sign up for cloudflare.

[pjbrunet]

8 million caching plugins is a total exaggeration. As far as I can tell there's only two options: WP Super Cache (which seems to have been abandoned by the author) and W3 Total Cache which is a spammy mess of nag screens to join New Relic and MaxCDN. (No wonder it was banned by WP-Engine.) If I wasn't busy on other projects, I would take on W3 Total Cache--it's the worst UI I have ever seen and it doesn't even work. I had to mostly disable it today because my CPU went from 100% to 600% after installing it.

[gibrown]

FYI, WP Super Cache is not really abandoned. The plugin author works for Automattic (as do I). I would say more that it has been so popular that support has been hard to keep up with and there hasn't been much focus on new features recently. Patches are always welcome: https://github.com/Automattic/wp-super-cache/

[juliangregorian]

Seeing a lot more than two: https://wordpress.org/plugins/tags/cache

[jdub]

How many big WordPress sites do you reckon can say, "Fuck it, it's all static anyway"? I mean, your blog, sure, but the New York Times?

(Who are, interestingly enough, putting a non-PHP-based high performance dynamic front-end in front of WordPress using... WP-API.)

[nkozyra]

Cloudflare is - in this example - just one of the 8 million (albeit as a CDN, a far wiser choice).

Ultimately that sacrifice comes down to real-time dynamic site versus having some content be static or conditionally dynamic. None of that is a symptom of PHP as the backend (unless you have a LOT of traffic).