I've been bringing this topic up with anyone I could get my hands on from PHP's internals for the last few years, looks like someone is tackling it! I think (🤞) this could have one of the biggest impacts on performance in PHP apps in a while Most PHP apps spend most of their time doing IO (not using the CPU). Except for N+1 problems, interacting with the DB is often fast. But calling APIs (via HTTP) can take a very long time. Very different orders of magnitude. Why? Because it establishes a TPC and HTTPS connection every time. That can take 100ms or 200ms (HTTPS is bonkers). On *every* request, because PHP (with FPM) recreates a connection every time. That's why switching to Laravel Octane or Symfony Runtime makes such a difference sometimes: by keeping the PHP process alive between requests, we can save these 100ms. Comparing that to what we save on the framework boot time, this is massive. The RFC proposes to share HTTP connections between requests in PHP-FPM: that's huge because it could bring some of these gains to all PHP apps out there, without having to switch to Octane/Runtime (and the downsides that come with it)