{"id":391,"date":"2025-08-27T20:55:37","date_gmt":"2025-08-27T20:55:37","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=391"},"modified":"2025-08-27T20:55:39","modified_gmt":"2025-08-27T20:55:39","slug":"optimizing-laravel-for-high-concurrency-with-octane","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/optimizing-laravel-for-high-concurrency-with-octane\/","title":{"rendered":"Optimizing Laravel for High Concurrency with Octane"},"content":{"rendered":"\n

Optimizing Laravel for High Concurrency with Octane<\/strong><\/h2>\n\n\n\n

By default, Laravel boots the entire framework on every request. This design is flexible but adds overhead. Laravel Octane<\/strong> removes that overhead by keeping the app in memory between requests using Swoole<\/strong> or RoadRunner<\/strong>. The result? Apps that handle thousands of requests per second with minimal latency. In this guide, we\u2019ll install Octane, configure workers, run benchmarks, and compare results.<\/p>\n\n\n\n

<\/div>\n\n\n\n\n

1 – Install Octane<\/strong><\/h2>\n\n\n\n

Install Octane and choose a server engine. Swoole is the most feature-rich option.<\/p>\n\n\n

composer require laravel\/octane\nphp artisan octane:install\n<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
This installs Octane\u2019s service provider and config. You\u2019ll be asked to choose Swoole or RoadRunner. Swoole provides task workers, coroutines, and better concurrency support.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
2 – Running Octane<\/strong><\/h2>\n\n\n\n
You can run Octane with Artisan. By default, it uses port 8000.<\/p>\n\n\n
php artisan octane:start --server=swoole --port=8000\n<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
This boots Laravel once, then keeps it in memory across requests. Startup overhead (autoloading, config, service providers) is eliminated on subsequent requests.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
3 – Worker Configuration<\/strong><\/h2>\n\n\n\n
Octane uses workers to handle requests. Configure workers in config\/octane.php<\/code>.<\/p>\n\n\n
\/\/ config\/octane.php (snippet)<\/span>\n'workers'<\/span> => 8<\/span>,\n'task_workers'<\/span> => 4<\/span>,\n'max_requests'<\/span> => 1000<\/span>,\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
workers<\/code> are processes handling HTTP requests. task_workers<\/code> run async tasks like broadcasting or sending emails. max_requests<\/code> controls how many requests a worker handles before restarting (to free memory leaks).<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
4 – Benchmarking Octane<\/strong><\/h2>\n\n\n\n
Let\u2019s compare performance using ab<\/code> (Apache Bench) or wrk<\/code>. First, test the default PHP-FPM setup:<\/p>\n\n\n
# Default PHP-FPM (without Octane)<\/span>\nab -n 1000 -c 50 http:\/\/127.0.0.1:8000\/\n<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Typical result: ~200 requests\/sec with ~50ms latency.<\/p>\n\n\n
# With Octane + Swoole<\/span>\nab -n 1000 -c 50 http:\/\/127.0.0.1:8000\/\n<\/code><\/span>Code language:<\/span> Bash<\/span> (<\/span>bash<\/span>)<\/span><\/small><\/pre>\n\n\n
Typical result: ~1,500 requests\/sec with ~5ms latency. That\u2019s a 7x performance boost<\/strong> just by running under Octane.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
5 – Octane Tasks<\/strong><\/h2>\n\n\n\n
Swoole\u2019s task workers let you run async jobs without queues. This is useful for lightweight background tasks.<\/p>\n\n\n
\/\/ routes\/web.php<\/span>\nuse<\/span> Laravel<\/span>\\Octane<\/span>\\Facades<\/span>\\Octane<\/span>;\n\nRoute::get('\/report'<\/span>, function<\/span> ()<\/span> <\/span>{\n    Octane::concurrently([\n        fn () => DB::table('users'<\/span>)->count(),\n        fn () => DB::table('orders'<\/span>)->count(),\n    ]);\n});\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This runs multiple DB queries concurrently inside Octane. Great for speeding up dashboards and reports. For larger workloads (like sending thousands of emails), stick to queues<\/a>.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
6 – Combining Octane with Caching<\/strong><\/h2>\n\n\n\n
Octane boosts raw performance, but combining it with Redis caching<\/a> makes apps both fast and efficient. Cached queries served from memory under Swoole can drop response times to under 2ms.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
7 – Monitoring Octane Performance<\/strong><\/h2>\n\n\n\n
Octane removes Laravel\u2019s per-request boot, which means memory leaks or long-running tasks can degrade performance. Monitor with Telescope<\/a> or external tools like New Relic and Blackfire.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
Laravel Octane is a game-changer for high concurrency. By keeping the app in memory, Octane delivers massive performance boosts with minimal changes to your code. We installed Octane, configured workers, benchmarked performance, ran concurrent tasks, and combined it with caching. With proper monitoring and queues, Octane lets Laravel handle enterprise-scale traffic with ease.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
What\u2019s Next<\/h2>\n\n\n\n