Weave Code
Octane Laravel Package
laravel/octane
Laravel Octane boosts your app's performance by serving it with high-powered servers like FrankenPHP, Open Swoole, Swoole, and RoadRunner. It boots your application once, keeps it in memory, and handles requests at supersonic speeds.
Supercharge your Laravel application's performance.
Frequently asked questions about Octane
- What is Laravel Octane used for?
- Laravel Octane supercharges Laravel application performance by booting the app once, keeping it in memory, and serving requests through high-performance servers such as FrankenPHP, RoadRunner, Swoole, and Open Swoole. It is suited to high-traffic APIs, SPAs, real-time systems, microservices, and monolithic Laravel apps that need lower latency and higher throughput without rewriting core logic.
- How do I install Laravel Octane?
- Install the package with Composer using composer require laravel/octane, then run the Octane install command to publish configuration and choose a server such as FrankenPHP, RoadRunner, Swoole, or Open Swoole. You will also need the matching server runtime or PHP extension and a reverse proxy where required. The official Laravel documentation covers server-specific setup steps.
- Which Laravel and PHP versions does Laravel Octane support?
- The assessment notes Laravel 10+ as a prerequisite, with Octane 2.x supporting LTS versions and Octane 3.x targeting Laravel 13. Octane requires PHP 8.1 or newer, with PHP 8.5+ recommended for full feature parity. Always check the package constraints for your exact Laravel and PHP combination.
- Which application servers can Laravel Octane use?
- Octane supports FrankenPHP, RoadRunner, Swoole, and Open Swoole. FrankenPHP bundles Caddy and is often preferred for stability, while RoadRunner and Swoole typically need a reverse proxy such as Nginx, Traefik, or Caddy. The servers are interchangeable, so you can choose based on your concurrency model and operational fit.
- How do I configure Laravel Octane?
- Configuration is published during installation and covers server choice, worker settings, memory limits, and hot-reload watch options. You can tune OCTANE_MAX_MEMORY and exclude vendor directories from watch lists to avoid hot-reload conflicts. Server-specific settings such as reverse proxy rules, HTTP/2 support, and worker pools also need configuration.
- Is Laravel Octane safe for stateful Laravel applications?
- Octane keeps workers in memory across requests, so stateful applications need care to avoid race conditions and stale state. Session handling, static properties, and shared memory must be designed for concurrency. Async-aware middleware generally works, but sync-only middleware and some third-party packages may need adjustment or testing.
- How do I test a Laravel Octane application?
- Test your application normally, then add coverage for async behavior using tools such as Octane::concurrently() and profile with Xdebug where needed. Pay attention to middleware that may behave differently in persistent workers and to packages that may not support async execution. Also test worker restarts, memory limits, and hot-reload behavior in a staging environment.
- What are common production concerns with Laravel Octane?
- Worker memory leaks are a high-impact concern, so monitor memory usage and configure OCTANE_MAX_MEMORY. Persistent database connections can leak or require tuning, especially PDO persistent connections for MySQL or PostgreSQL. Server-specific issues may appear under high concurrency, and deployment pipelines need adjustment for hot reloads and worker restarts.
- What are alternatives to Laravel Octane?
- Traditional PHP-FPM with Nginx or Apache remains the default alternative, while Octane itself abstracts FrankenPHP, RoadRunner, Swoole, and Open Swoole. You can also evaluate those servers directly, but Octane provides Laravel integration and server abstraction. Choose based on whether you need in-memory bootstrapping and async I/O versus simpler deployment.
- How much performance improvement does Laravel Octane provide?
- Octane typically offers 2–10x improvements, but the exact gain depends on your application, server choice, and workload. CPU-bound requests may favor Swoole, while I/O-bound workloads may fit RoadRunner or FrankenPHP. Benchmark your current RPS and P99 latency before and after adoption.
Weaver
How can I help you explore Laravel packages today?