31 seconds per page
PHP ran via CGI, so the bytecode cache never survived a single request — Laravel recompiled about 2,000 files every time. Switched on the OPcache disk cache.
- Heaviest page, s
- 31 1
- Home page, s
- 3.4 1.7
DevOps and Linux server administration: setup and tuning of Nginx, PHP-FPM, MariaDB/MySQL and Redis; zero-downtime migrations between servers; backup systems with off-site storage; security — fail2ban, firewall, WAF; Docker deployments.
I work with VPS and dedicated servers from any provider, with control panels (HestiaCP, cPanel, ISPmanager) or without them. The goal is production that stays up under load and recovers quickly when something breaks.
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Service
Measured before the work started and after delivery. Client names stay private — only the numbers.
PHP ran via CGI, so the bytecode cache never survived a single request — Laravel recompiled about 2,000 files every time. Switched on the OPcache disk cache.
A catalogue search with no index at all ran for 400 seconds and choked the database — visitors got 503 errors. Three database indexes later, the problem was gone.
before after