We had a booking system on PHP 8.1, running on a mix of app servers in UTC and a couple of legacy boxes still on Europe/London. A nightly report summed "bookings in the next 7 days" and the number was
We run a PHP 8.2 worker pool on Kubernetes, 60 pods, each processing image derivatives from an S3-style bucket. Each job: download, resize with GD, write back. Throughput was fine—about 40 jobs/sec ac
PHP 8.1 on three FPM pools behind an ALB, Debian 11, APCu 5.1.21 with apc.enable_cli=0. We cache a per-currency pricing table built from a 12k-row product matrix; the array is roughly 4MB serialized,
PHP 8.1, Ubuntu 22.04, php-fpm plus a systemd timer that ran `bin/console billing:charge-due` every five minutes. Table `subscriptions` had about 400k rows, maybe 3k due on any given night. The job to
We had a reporting job on PHP 8.1.27, Debian 12, 8 vCPU worker, pulling about 120k invoice rows nightly from MySQL 8.0 and writing a CSV per customer. Each customer's rows came back already ordered by
We run PHP 8.2.14 on Ubuntu 22.04, PHP-FPM with 32 workers, MySQL 8.0 on the same host. After upgrading a staging box to 8.3.0, one endpoint went from p95 180ms to p95 2.4s. It served paginated JSON:
We run PHP 8.2.15 CLI workers on Debian 12, consuming from a MySQL 8.0 queue table via long-lived processes managed by Supervisor. Each worker handles roughly 40k jobs per day, and we cap them at 400M
We run PHP 8.2 with pdo_mysql against MySQL 8.0 on RDS. Our write path pulls roughly 40k events/hour into a `events` table where one column, `payload`, is `TEXT`. One Tuesday the analytics team asked
Staging ran PHP 8.2 on FPM with a shared NFS mount for releases, ~180 files per deploy, and opcache.validate_timestamps=0. Deploys were atomic symlink swaps, so we assumed nothing needed revalidation.
PHP 8.2.13, built-in server (`php -S`), PHP-FPM not involved. A throwaway internal tool: a router script that serves uploaded files, roughly 40k small JSON files on disk, one developer machine, macOS
We run PHP 8.1 with PHP-FPM and Nginx on AWS, handling about 500 req/s across 12 FPM pools. Last month, the slow log flagged a batch of requests taking 5-8 seconds, but our application logs showed sub
PHP 8.1.14, Alpine containers, eight `queue:work` processes per host, each capped at `memory_limit=512M` by a supervisor config nobody had touched in two years. The symptom: workers would vanish every
PHP 8.2 on Ubuntu 22.04, PHP-FPM with Redis session handler, sessions stored via `session.serialize_handler = php`. A customer reported being logged out at random, roughly once a day, always after a l
A 5.6-era app I inherited had this line in `composer.json`:
A checkout endpoint on Laravel 10.43, PHP 8.2.19, MySQL 8.0.36, running on three FPM pods behind an ALB with 30s idle timeout. Average order value write is one INSERT into orders plus an INSERT into o
A queue worker on PHP 8.2 / MySQL 8.0.36 started silently matching zero rows on a lookup that had passed staging. The table was small — about 120k rows in `orders`, indexed on `(tenant_id, external_id
Setup: PHP 8.2.13, php-fpm 8.2.13, Debian 12, 32 vCPU / 128 GB, opcache with `opcache.memory_consumption=512`, `opcache.max_accelerated_files=65536`, `opcache.validate_timestamps=0`. We added `opcache
上周把一个小服务从 8.1 升到 8.3，升级完压测，某个接口的 P99 从 40ms 涨到 180ms。第一反应是数据库，抓了慢日志，一条都没有。第二反应是 OPcache 没生效，查了 `opcache_get_status()`，命中率正常。
