> "One request = one freshly started process" This isn't true for all (most?) PHP applications today. PHP installations include the FastCGI Process Manager (ph

> "One request = one freshly started process" This isn't true for all (most?) PHP applications today. PHP installations include the FastCGI Process Manager (php-fpm). According to Wikipedia (https://en.wikipedia.org/wiki/FastCGI https://en.wikipedia.org/wiki/FastCGI), > Instead of creating a new process for each request, FastCGI uses persistent processes to handle a series of requests. According to the PHP Internals book (https://www.phpinternalsbook.com/php7/memory_management/zend_memory_manager.html#the-two-main-kind-of-dynamic-memory-pools-in-php https://www.phpinternalsbook.com/php7/memory_management/zend...), is close to a "share-nothing architecture" thanks to custom implementations of `malloc()` and `free()` that know about the lifecycle of a request.