Compute and Capacity Settings
Manage compute limits, timeout values, and database capacity for project workloads.
Configure compute limits, timeout values, and database scaling boundaries for your project workloads.
This guide covers pending compute changes and the deployment cycle that applies them.
About the Compute Lifecycle
Compute settings use a pending and current lifecycle. When you change timeout, virtual central processing unit (vCPU), or Aurora Capacity Unit (ACU) values, the control plane stores the new values as pending.
Pending values do not change active Amazon Web Services (AWS) resources immediately. monolayer promotes pending values to current values during the next successful production deployment.
Adjusting Workload Limits
Follow these steps to update application, task, or cron limits, and queue new timeout and vCPU values for your next production deployment.
Before you start
Ensure you know the workload type you want to tune: Application, Tasks, or Crons.
Steps
- Choose Settings > Compute in the project sidebar.
- Type or select the timeout and vCPU values in the target workload panel.
- Click Save in that panel.
What happens next
The control plane stores the new values as pending settings for your next production deployment.
Scaling Database Capacity
Follow these steps to update serverless database capacity and queue new minimum and maximum ACU boundaries for your database.
Before you start
Your project must define a supported database workload.
Steps
- Choose Settings > Compute in the project sidebar.
- Type the minimum and maximum ACU values in the target Postgres or MySQL panel.
- Click Save in the database panel.
What happens next
The control plane stores the new database capacity boundaries and applies them during your next production deployment.