5 ms·
I recently wrote up my Caddy+Varnish+PHP-FPM solution for WordPress[0]. It's fairly complementary to the steps detailed in the OP. The site absolutely flies now
by mwpmaybe 10y ago
I recently wrote up my Caddy+Varnish+PHP-FPM solution for WordPress[0]. It's fairly complementary to the steps detailed in the OP. The site absolutely flies now: 50-75ms response times cf. 200-300ms per Google, A+ on SSL Labs cf. unencrypted HTTP/1.1, and the $10/mo VPS rarely cracks 1% CPU utilization despite it being a modestly well-trafficked site. Our organic search position has improved significantly.
Caddy was maybe an odd choice but it performs well and it's been a breath of fresh air after dealing with some gnarly NGINX and Apache configurations in the past. So far it's been easy to maintain and there's a clear CDN migration path (Fastly). I'm using Docker's official PHP-FPM images[1] to serve multiple sites with some isolation, sharing Caddy, Varnish, and MariaDB instances.
I'm not sure if this solution has value for anyone else but I've been plugging it here and there in case there is!
0. https://gist.github.com/mwpastore/f42f6f1309a7b067519f4c08e18b0b6a https://gist.github.com/mwpastore/f42f6f1309a7b067519f4c08e1...
1. https://hub.docker.com/_/php/ https://hub.docker.com/_/php/
- basch 10y agohave you tested what happens if you substitute in HHVM
- mwpmaybe 10y agoI have not. The whole purpose of an architecture like this is to turn WordPress into a glorified static site generator, so it doesn't particularly matter how fast (or slow) the application server is. At any rate, I thought PHP 7 was about as fast as (and even faster than, in some cases) HHVM?