-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluate webserver integration #65
Comments
Probably, we must leave this to the user level PHP scripts that implement SAPI or run as an Async server |
There are many exciting things to work on in this issue. Some ideas:
https://stackoverflow.com/a/2772929 |
It is easier to see how an event driven approach like the links you posted above can benefit |
from a business perspective, people prefer PHP-FPM more than mod_php Reasons:
To note: PHP supports a feature called preloading: https://www.php.net/manual/en/opcache.preloading.php |
People are moving to Swoole and other implementations, cos classical PHP-FPM doesn't scale well when compared to other technologies like NodeJS Swoole solves this by going async, but this introduces very ugly async code and you can't do anything other than plain IO, The majority of the applications use classic PHP-FPM, and there is no real-world performance benefit even with the introduction of PHP-8-JIT, because the classical FPM is single-threaded and spawns child processes based on max child processes that you configure. A single FPM process will block as long as it finishes with the entire request. This is one area, which we could improve on and deliver some real-world performance improvements,
|
PHP SAPI: https://github.com/php/php-src/tree/master/sapi
The text was updated successfully, but these errors were encountered: