Server response time graph
Posted: Wed Jan 22, 2025 5:54 am
For a more accurate comparison of servers, it is worth dividing them into two groups:
Servers that initialize the application on each request: Apache mod_php, PHP-FPM, Nginx Unit.
Servers with long-lived processes that load the kazakhstan telegram number database application once and continue working with it: FrankenPHP, Swoole, RoadRunner.
In the first group (Apache mod_php, PHP-FPM, Nginx Unit) the difference in RPS is insignificant. However, PHP-FPM and Nginx Unit are more efficient in terms of resource usage.
Benchmarks often compare PHP-FPM and mod_php using static data (e.g. phpinfo output). In such cases, PHP-FPM does show a 300%+ performance boost, which is only relevant for static data.
Examples of testing phpinfo output:
PHP-FPM – https://clck.ru/3DeQ32
Apache+mod_php – https://clck.ru/3DeQbP
The server response time in the case of Apache increases to 8 seconds. While PHP-FPM consistently delivers pages in 200-300 ms.
Result of testing phpinfo with Apache+mod_php
Result of testing phpinfo with PHP-FPM
Testing complex applications such as Bagisto shows that under dynamic loads the difference between PHP-FPM and mod_php is minimal.
The second group (FrankenPHP, Swoole, RoadRunner) are long-lived processes. They provide a significant reduction in resource consumption and a significant increase in RPS compared to the first group. However, it is important to consider that the application must be adapted to work with servers that are loaded into memory once and continue to function without re-initialization.
Community and Support
Applications like Swoole, RoadRunner, FrankenPHP, and Nginx Unit have strong community support. Let's compare the level of support.
Servers that initialize the application on each request: Apache mod_php, PHP-FPM, Nginx Unit.
Servers with long-lived processes that load the kazakhstan telegram number database application once and continue working with it: FrankenPHP, Swoole, RoadRunner.
In the first group (Apache mod_php, PHP-FPM, Nginx Unit) the difference in RPS is insignificant. However, PHP-FPM and Nginx Unit are more efficient in terms of resource usage.
Benchmarks often compare PHP-FPM and mod_php using static data (e.g. phpinfo output). In such cases, PHP-FPM does show a 300%+ performance boost, which is only relevant for static data.
Examples of testing phpinfo output:
PHP-FPM – https://clck.ru/3DeQ32
Apache+mod_php – https://clck.ru/3DeQbP
The server response time in the case of Apache increases to 8 seconds. While PHP-FPM consistently delivers pages in 200-300 ms.
Result of testing phpinfo with Apache+mod_php
Result of testing phpinfo with PHP-FPM
Testing complex applications such as Bagisto shows that under dynamic loads the difference between PHP-FPM and mod_php is minimal.
The second group (FrankenPHP, Swoole, RoadRunner) are long-lived processes. They provide a significant reduction in resource consumption and a significant increase in RPS compared to the first group. However, it is important to consider that the application must be adapted to work with servers that are loaded into memory once and continue to function without re-initialization.
Community and Support
Applications like Swoole, RoadRunner, FrankenPHP, and Nginx Unit have strong community support. Let's compare the level of support.