3 ms·
Sorry folks! Desperately trying to fix it now...
by smartial_arts 14y ago
Sorry folks! Desperately trying to fix it now...
- runarb 14y agoTried WP Super Cache?
- smartial_arts 14y agoNo, I haven't. Had no reason, really, just trying to fix it on nginx/php-fpm level at the moment.
- grandpa 14y agoIf it's an interesting fix, please consider doing a post like "What I learned from getting slashdotted by Hacker News".
- smartial_arts 14y agoI am by no means a devops guy, and this is just a quickly whipped together t1.micro instance with haproxy/nginx/php-fpm/wp/whatever, that's been built using tutorials of questionable quality (as it turned out now) that I found online. So there probably won't be too much value in a post like that. All I did was setting some sane parameters for Fast CGI stuff in nginx, some for php-fpm and the db.
- rogem002 14y agoI'm guessing you have root control of the server? Install Varnish, it's a reverse proxy that caches request results in the RAM.