Scaling LAMP doesn't have to suck
summary
Concrete steps to scale a LAMP stack by separating services into VMs or Docker containers, tuning Linux (open files, network ports, deadline I/O scheduler) and replacing components: use nginx instead of Apache, Percona Server for MySQL, Redis plus Resque for cache and queues, and PHP-FPM with OPcache sized statically (workers ≈ cores×4). Measured results include nginx serving ~21,000 requests using ~10% of a 12‑core CPU and 160MB RAM, switching CFQ→deadline giving ~50% more disk IOPS, and recommendations to run Debian, recent kernels and PHP 5.5+.
AI-written summary · about
related talks
32mWordPress Scalability
36mApache, nginx, Docker and the Swear Words We Love
24mGrowing Your Laravel Application Infrastructure
58mMassively Scaled High Performance Web Services with PHP
31mFrom Runtime to Resilience: Scaling PHP
47mFrom Legacy to High-Load: Evolution of a Web Application
39mPHP Performance Demystified - Measure, Understand, Optimise
44mIntroduction to application scaling