Laravel Octane vs PHP-FPM: what actually changes
Octane keeps the application booted between requests. That saves boot time per request — and breaks any code that assumes a fresh process.
PHP normally boots the framework on every request. Octane runs a long-lived worker and reuses it, cutting the per-request overhead. The gain is real but bounded, and it comes with rules about state.
What you gain
Framework boot, service provider registration and config loading happen once per worker instead of once per request. On a simple app that is a few milliseconds; on a heavy app with many providers it is more. The gain shows up as throughput under concurrency rather than a dramatic single-request speedup.
What breaks
Anything stored in a static property, a singleton that accumulates data, or a global that assumes one request per process. Memory leaks become visible because the process lives for hours. Containers resolved as singletons must be safe to reuse.
Operational differences
Workers must be reloaded on deploy, and a memory limit becomes a hard ceiling rather than a per-request one. Logging and error reporting need to distinguish worker restarts. You will also want a supervisor that restarts crashed workers promptly.
When to adopt it
After the database and caching work is done, when you have steady traffic and a reason to squeeze the last 20–30% of throughput. For a brochure site or an app serving a few requests per second, PHP-FPM with OPcache is simpler and fast enough.
Frequently asked questions
Is Octane a replacement for caching?
No. It reduces framework overhead per request; it does nothing for a slow query. Fix the query first.
Swoole or RoadRunner?
RoadRunner is simpler to install and debug; Swoole offers more features if you need them. For most Laravel apps the difference is operational preference.
More on this topic: Performance & SEO articles.
Admin
Related articles
Internal linking: the cheapest SEO work you are not doing
Every important page should be linked from somewhere with descriptive anchor text. It costs nothing and it compounds.
Getting a new site indexed by Google: a checklist that works
Verify Search Console, submit a sitemap, make sure nothing is blocking crawl, and then be patient. Most indexing problems are self...
How to speed up a slow WordPress site without rebuilding it
Hosting, page cache, images and plugins — in that order. Most slow WordPress sites improve dramatically before any theme work.