Scaling Resources
Unleashed databases can be scaled to match your application's needs. Adjust CPU, memory, and storage through the dashboard.
Prerequisites
- An Unleashed subscription
- A database with RUNNING status
Note: FREE tier databases cannot be scaled. Upgrade to Unleashed to access scaling features.
How to Scale
- Navigate to Databases in the sidebar
- Click on your database name
- In the Scale Settings section, adjust the sliders for:
- CPU - Processing power
- Memory - RAM allocation
- Storage - Disk space
- Click Apply Changes
- Confirm the changes in the dialog
Resource Limits
| Resource | Minimum | Maximum |
|---|---|---|
| CPU | 0.1 cores | 1 core |
| Memory | 256 MB | 16 GB |
| Storage | 256 MB | 50 GB |
Important Considerations
Database Restart
Changing CPU or memory will briefly restart your database. Plan scaling operations during low-traffic periods when possible.
Storage changes do not require a restart.
Status During Updates
While scaling, your database status will show:
- UPDATING - Changes are being applied
- RUNNING - Changes complete, database is operational
- UPDATE_FAILED - Something went wrong (see error details)
The scale settings are disabled while the database is updating.
Storage Can Only Increase
Storage allocation can only be increased, not decreased. Choose your initial storage size carefully.
Scaling Recommendations
When to Scale CPU
Increase CPU if you notice:
- Slow query execution
- High CPU utilization in monitoring
- Request timeouts under load
When to Scale Memory
Increase memory if you experience:
- Out-of-memory errors
- Slow queries due to disk spillover
- Poor cache hit rates
When to Scale Storage
Increase storage before you reach capacity:
- Monitor storage usage regularly
- Plan for data growth
- Leave headroom for logs and temporary files
Troubleshooting
Cannot Modify Resources
- Verify you have an Unleashed subscription
- Check that the database status is RUNNING
- Ensure you're not already at the maximum resource limits
Update Failed
If scaling fails:
- Check the error message on the database detail page
- The database should remain operational with previous settings
- Try the scaling operation again
- Contact support if the issue persists