Framework Competition — Volucer (spawn_cgi)

Volucer's `spawn_cgi` backend: volucer runs the app's entry script through a fresh `php-cgi` for every request, so the framework's boot is inside the request clock — the same shape as nginx + PHP-FPM, in a different server. The php-cgi pool is reached over a unix socket, not loopback TCP, so this arm differs from the FPM arm by its SERVER and never by its transport. End-to-end HTTP over loopback — includes the constant webserver overhead. Single sequential client.

PHP 8.5.11 · Linux 6.8.0-139-generic · volucer-cgi mode · 1000 iterations per run over 10 runs · charts show the median as a faint bar + dot with the fastest → p95 range, lower is better

Framework startup — per-request boot (Volucer spawn_cgi)
Framework startup — per-request boot (Volucer spawn_cgi)
Total response times
Total response times

Feature benchmarks

Routing

GET / — dispatches a request through the router and returns a rendered template — no database access. The `/echo` band runs the same path with a constant handler instead, so what the template render costs can be read off directly rather than inferred.

Routing
ORM / Active Record

GET /items — loads one page of the 1,000 seeded rows through each framework's ORM / Active Record layer: 20 items plus a COUNT for the pagination total. The `-fast` band repeats that page with hydration switched off, so the cost of building one object per row can be read directly instead of inferred.

ORM / Active Record
Query Builder

GET /items-qb — builds the same page of 20 items with each framework's query builder instead of its ORM, so the two data-access styles can be compared directly.

Query Builder
REST API (JSON)

GET /api/items — serves the same page of items as a JSON response rather than HTML, which adds serialization to the ORM work. The `-fast` band repeats that response with hydration switched off, so serialization cost and hydration cost can be told apart.

REST API (JSON)
AOP (Aspect-Oriented)

GET /features/aop — runs a request through an interceptor pipeline — logging, retry and middleware aspects wrapped around the handler. Only frameworks with an AOP layer take part.

AOP (Aspect-Oriented)
Cache

GET /features/cache — reads a COUNT(*) over the 1,000 rows through the framework's cache with a 10-second TTL, so a hit costs no database work and a miss runs the query.

Cache
Database Events

GET /features/db-events — inserts one event row per request and lets the framework's database events fire around that write.

Database Events
Event Dispatcher

GET /features/events — dispatches an in-process event to registered listeners.

Event Dispatcher
Validation

GET /features/validation — validates a payload with the framework's own validator.

Validation
Config

GET /features/config — resolves a value from the framework's config repository.

Config
Request-Scoped Services

GET /features/request-scoped — resolves a service scoped to the request from the container.

Request-Scoped Services
Rate Limiter

GET /features/rate-limit — checks a cache-backed rate limiter.

Rate Limiter

Latency by endpoint (ms, trimmed mean — lower is better)

RequestWorkloadAzeraLaravelSymfonySpiralCodeIgniterCakePHP
GET /no DB — routing + template only0.6493.691.896.681.811.38
GET /echono DB — routing + dispatch only0.5523.581.676.601.661.25
GET /items20 of 1000 items (page 1, + COUNT)1.414.793.457.722.622.69
GET /items-fast20 of 1000 items (page 1, + COUNT), hydrated rows not built1.324.523.387.562.512.66
GET /items/11 item by id1.284.522.817.512.422.51
POST /items1 row upserted (sentinel #999999)1.474.563.827.612.602.68
GET /items-qb20 of 1000 items (page 1, + COUNT)1.274.352.507.262.472.18
GET /items-qb/11 item by id1.204.232.447.162.392.07
POST /items-qb1 row upserted (sentinel #999997)1.314.333.387.292.622.20
GET /api/items20 of 1000 items as JSON1.274.682.796.842.462.41
GET /api/items-fast20 of 1000 items as JSON, rows not hydrated1.184.272.746.692.362.36
GET /api/items/11 item by id as JSON1.204.522.606.732.372.42
POST /api/items1 row upserted (sentinel #999998)1.274.413.616.812.472.56
GET /features/aopno DB — interceptor pipeline2.445.193.218.16——
GET /features/cacheCOUNT(*) of 1000 rows, cached 10s (miss = query)1.484.462.807.382.322.30
GET /features/logno DB — buffered log handlers1.073.641.806.78——
GET /features/retryno DB — retry policy1.053.651.816.89——
GET /features/pipelineno DB — middleware pipeline0.6063.641.787.03——
GET /features/db-events1 event row INSERTed per request1.564.412.967.812.582.50
GET /features/eventsno DB — in-process listeners1.524.122.297.452.491.87
GET /features/validationno DB — validator run0.5974.572.136.932.111.70
GET /features/configno DB — config lookup0.5483.621.806.811.781.29
GET /features/request-scopedno DB — scoped service resolve0.5703.611.796.811.761.28
GET /features/rate-limitno DB — cache-backed limiter0.5583.761.826.891.771.40

Server floor — real nginx + PHP-FPM with pm.max_requests=0: the pool never recycles its worker, so no process is spawned per request — what remains is the FastCGI handshake plus a minimal script. A hello-world endpoint that boots nothing but PHP (floor-php) and a static file through nginx (floor-http) measure exactly that cost — the floor every row stands on. Subtracting that floor leaves the framework's own per-request boot, which FPM still pays for every request even though its worker survives.