<a href="https://vulke.medium.com/frankenphp-vs-php-fpm-part-3-cpu-memory-and-the-hidden-cost-of-doing-nothing-92bfee7b00a5" target="_blank" rel="noopener nofollow">https://vulke.medium.com/frankenphp-vs-php-fpm-part-3-cpu-memory-and-the-hidden-cost-of-doing-nothing-92bfee7b00a5</a>
<img src="https://media.daily.dev/image/upload/s--GHoZPctB--/f_auto/v1757358909/ugc/content_a6b2b086-d1de-4645-a83c-b264ae468308?_a=BAMClqZW0" alt="image">
Long story short:
<blockquote>
Use FrankenPHP (especially with workers) if:
You’re running high-traffic applications or APIs that receive constant traffic.
You want lower latency and higher throughput per container or per VM.
You benefit from built-in server capabilities (like static file serving, Caddy integrations, HTTP/2/3).
You’re building modern, containerized applications and want to reduce server complexity.
</blockquote>
Warning!!! Article posted on 	~~piece of sh.t ~~ “medium” so sometimes they ask money, but article too good to avoid posting

Code Distilled is a filter for s..t like ad posts, and fluff like “Top 10 Tools for *” Every piece is carefully reviewed to share only valuable, professional insights. No noise, just pure, distilled!!!

Feel free to try post your article :)

Code Distilled

A performance comparison between FrankenPHP and PHP-FPM examining CPU usage, memory consumption, and operational costs. The analysis reveals that FrankenPHP with workers offers superior performance for high-traffic applications, providing lower latency and higher throughput. The comparison includes recommendations for when to choose each solution based on traffic patterns and infrastructure requirements.

FrankenPHP vs PHP-FPM

The benchmark is incomplete, because the impact on latency and throughput of the HTTP server is not mentioned. We don’t even no what HTTP server was used and how it was configured. I also tested FrankenPHP against my performance optimized nginx HTTP server with FPM and there was no actual performance difference.
FrankenPHP comes with an optimized Caddy web server and if you don’t optimize nginx when comparing it against FPM you can’t get authentic benchmarks.
I acknowledge the good default settings in FrankenPHP and that it comes with Let’s Encrypt. It’s a simple and complete HTTP runtime environment for PHP that offers good performance out of the box. But it’s not better than an optimized nginx+FPM and in worker mode not better than Openswoole/Swoole.

It’s important for me to clarify, that I have not read the article, but I have read the title and the meme/image here on daily.dev. My thoughts, avoid premature optimization, yes. If you have 20 daily active users and you already have a webserver and PHP-FPM setup which works, then stick with it. But if you’re either experiencing performance issues, then consider optimizing your existing setup or switch to Frankenphp. But if you’re starting a new project, I see no reason to not just go for Frankenphp from the start, with the great default settings and performance and Auto-SSL. Also an easy upgrade path to use workers if you need even more performance. Safe to say, I’m fan of Frankenphp, but also of things that makes sense!

Just BTW: Medium is fine. I pay for it and I get valuable content on it. Other people get payed for creating content.

no one mentioned the ability to mount everything under project root to /app in frankenphp docker and it would automagically run our laravel app? this feature alone is so much worth switching to it