<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Muhammet Şafak — Service &amp; load research</title><description>Latency distribution, saturation point and queue behaviour under load — p95/p99, not the mean; backpressure and circuit breakers included.</description><link>https://www.muhammetsafak.com.tr/</link><language>en-US</language><lastBuildDate>Fri, 18 Sep 2026 00:00:00 GMT</lastBuildDate><managingEditor>info@muhammetsafak.com.tr (Muhammet Şafak)</managingEditor><atom:link href="https://www.muhammetsafak.com.tr/en/research/program/servis-yuk/rss.xml" rel="self" type="application/rss+xml"/><item><title>One core carries 14,330 OAuth2 requests in Go and 5,152 in PHP-FPM</title><link>https://www.muhammetsafak.com.tr/en/research/capacity-per-core-go-php-oauth2/</link><guid isPermaLink="true">https://www.muhammetsafak.com.tr/en/research/capacity-per-core-go-php-oauth2/</guid><description>On four cores Go carried 57,321 mixed requests a second, FrankenPHP 25,659 and php-fpm 20,606 — 14,330, 6,415 and 5,152 per core. The number that goes into a capacity plan is not that one but application CPU per request: 66.8, 110.7 and 187.7 microseconds. At saturation FrankenPHP uses only 2.84 of its four cores, against Go&apos;s 3.83 and php-fpm&apos;s 3.87. The database is not the constraint: on the same four cores PostgreSQL alone writes 68,212 rows a second, above the mixed ceiling of the fastest candidate.</description><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><category>servis-yuk</category><category>go</category><category>php</category><category>benchmark</category><category>oauth2</category><category>postgresql</category><category>frankenphp</category><category>php-fpm</category><category>capacity</category></item><item><title>Seven PHP frameworks under identical load: the gap narrows as soon as the request does real work</title><link>https://www.muhammetsafak.com.tr/en/research/php-framework-load-test/</link><guid isPermaLink="true">https://www.muhammetsafak.com.tr/en/research/php-framework-load-test/</guid><description>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&apos;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.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>servis-yuk</category><category>php</category><category>benchmark</category><category>framework</category><category>php-fpm</category><category>docker</category></item></channel></rss>