Compute

​

Introduction

Each environment deployed to Laravel Cloud runs on at least one App compute instance, which is assigned a specified amount of CPU processing power and available RAM.

Your environment’s App compute instance is responsible for handling incoming HTTP traffic to the environment. In addition, you may add dedicated worker compute instances to your environment to process queued jobs or execute other background processes.

Compute resources assigned to an environment may be managed from the environment’s infrastructure canvas dashboard.

​

App Compute Cluster

Your environment’s App compute cluster represents the primary compute and infrastructure that will run your Laravel application. This compute cluster can serve web traffic, hibernate, manage long-running processes like queue workers, and even run scheduled tasks.

To scale or customize your environment’s App compute cluster, simply click the cluster in your environment’s infrastructure canvas dashboard.

​

Laravel Octane

Laravel Cloud makes it easy to run your application using Laravel Octane, which boots your application once and keeps it in memory for each request.

When editing your App compute cluster, simply toggle on the “Use Octane as runtime” option. Then, save and deploy your environment and Laravel Cloud will build, configure, and serve your Laravel application using Laravel Octane and FrankenPHP.

Please review the Laravel Octane documentation to learn about the caveats you should keep in mind when building your application to run on Octane.

​

Worker Clusters

Worker clusters are optional compute resources that can be added to your environment. They are a mirror copy of your environment’s App compute in the sense that they use the same repository, branch, PHP version, environment variables, deployment commands, database, and other resources. However, each Worker cluster can be independently sized and can run a custom set of queue workers or custom background processes.

Dedicated worker clusters can be useful for larger applications where you want to use the primary App cluster to serve web traffic, but send background workloads to separate compute resources.

To add a worker cluster to an environment, click “Add worker cluster” on the environment’s infrastructure canvas dashboard.

​

Autoscaling

Laravel Cloud can automatically scale the compute resources attached to your environment based on the CPU and memory being used by the environment. To configure your environment’s autoscaling strategy, click on your environment’s App or Worker compute cluster on the infrastructure canvas dashboard, and select the autoscaling strategy that is appropriate for your environment.

For maximum flexibility, Laravel Cloud currently supports three different autoscaling strategies:

• None: run your App / Worker compute on a single instance without autoscaling.
• Custom: automatically scale your App/ Worker compute clusters up and down horizontally within a specified minimum and maximum replica range.
• Unlimited: automatically scale your App / Worker compute clusters up and down indefinitely based on demand.

After adjusting your environment’s autoscaling strategy, re-deploy the environment in order for the changes to take effect.

​

Compute Classes

Laravel Cloud applications run on the latest generation of AWS Graviton EC2 servers with an optimized cost to performance ratio, allowing us to pass on best-in-class compute performance and pricing.

Laravel Cloud offers two classes of compute:

Within each class, there are multiple sizes of CPU and RAM available. Prices vary by region.

​

Compute Metrics

Your environment’s compute metrics may be viewed by navigating to the “Metrics” tab of your environment. When graphed, your environment’s App and Worker clusters CPU and memory usage will be averaged across all replicas.

​

Hibernation

Your environment is able to hibernate if no requests are received within the specified time limit. Environments that enter a “hibernating” state will not be charged for compute until they are “woken up” again.

Hibernating environments will typically take 5-20 seconds to wake up, which will happen automatically when the environment receives a new HTTP request.

You can enable hibernation by clicking on your environment’s App compute cluster on the infrastructure canvas dashboard, enabling the Hibernation toggle, saving the compute cluster settings, and re-deploying the environment.

​

Hibernation, Scheduling, and Workers

When an environment has hibernation enabled and is hibernating, scheduled tasks will not be executed on the cluster. In addition, queue workers and custom background processes will not execute. These tasks will resume automatically if the environment is woken up.

​

Limitations

• Only Flex compute sizes are able to hibernate
• Hibernation takes place at the environment level. When an environment goes into hibernation, ALL compute clusters in the environment will hibernate. This includes worker clusters.