Skip to content
Muhammet Şafak
tr
All records

Research programme

Service & load

Latency distribution, saturation point and queue behaviour of a service under load — p95/p99, not the mean. Analysis of patterns like backpressure, circuit breakers and queuing belongs here alongside the measurements.

Where does a service saturate under load, and what happens there?

Open

1 records

Service & load Measurement

Seven PHP frameworks under identical load: the gap narrows as soon as the request does real work

On the same hardware, the same PHP build and the same seven routes, how many requests a second do Laravel, Symfony, CodeIgniter, Yii2, Phalcon, Laminas and Slim serve, and at what latency?

Finding

On an empty route the fastest is 4.4× the slowest (Slim 25,975, Laravel 5,966 req/s). As soon as the request does real work the gap closes: 3.7× for a single row from the database, 3.5× for twenty rows. Phalcon is third on an empty route and fifth once a query is involved — being a C extension buys nothing while the process waits on MySQL. And the expensive decision is not the framework: Laravel's own default `web` middleware group takes the same response from 5,858 to 2,176 req/s, so one default costs more than most of the distance between the frameworks.

Medium confidence

Search the site

Start typing to search posts, projects and pages.

Esc to close Powered by Pagefind