Scale Resources

Add more CPU, RAM, or disk space to handle increased load.

When to Scale

Signs you need more resources:

• ⚠️ Odoo is slow or timing out
• ⚠️ CPU usage consistently above 80%
• ⚠️ Memory usage above 85%
• ⚠️ Disk usage above 80%
• ⚠️ More concurrent users than before

Check Current Usage

1. Open your environment
2. Go to Monitoring tab
3. Review the metrics:
   • CPU: Should stay below 80%
   • Memory: Should stay below 85%
   • Disk: Watch for 80%+ warnings

Scale Up Resources

1. Open your environment
2. Go to Settings → Resources
3. Adjust the sliders:

CPU Cores

• Development: 1-2 cores
• Staging: 2-4 cores
• Production: 4-8+ cores

RAM (Memory)

• Development: 2-4 GB
• Staging: 4-8 GB
• Production: 8-16+ GB

Disk Space

• Small projects: 10-20 GB
• Medium projects: 20-50 GB
• Large projects: 50-100+ GB

4. Click Save
5. Click Deploy to apply changes

Note: Scaling requires a redeploy. Plan for 2-3 minutes of downtime.

Resource Guidelines by Users

Enable Performance Features

PgBouncer (Pro Plan)

Connection pooling for better database performance:

1. Go to Settings → Database
2. Enable PgBouncer Connection Pooling
3. Click Save and Deploy

Improves performance by 20-30% under load.

Read Replica (Pro Plan, Odoo 18+)

Offload read queries to a replica:

1. Go to Settings → Database
2. Enable Read Replica
3. Click Save and Deploy

Resource Impact: Replica uses 30% of primary CPU/RAM, 100% of disk.

Scaling Without Downtime

For production environments, minimize disruption:

1. Schedule during low traffic - Early morning or weekends
2. Notify users - Brief maintenance window
3. Scale up, not down - Reducing resources can cause issues
4. Test in staging first - Verify settings work

Check Quota Limits

Your organization has resource quotas:

1. Go to Settings → Usage
2. See your limits:
   • Total CPU cores
   • Total RAM
   • Total disk space
3. If at limit, upgrade your plan or contact support

Cost Considerations

Scaling affects your bill:

• More resources = higher cost
• Development environments - Keep small, stop when not in use
• Production - Size appropriately for your load

Tip: Right-size your environments. Don't over-provision "just in case."

Troubleshooting

"Quota exceeded"

You've hit your organization's resource limit:

1. Reduce resources on other environments
2. Stop unused environments
3. Upgrade your plan

Performance didn't improve

Check for:

• Slow database queries (need optimization, not more CPU)
• Missing database indexes
• Inefficient custom code
• External API bottlenecks

Out of disk space

1. Clean up old filestore attachments
2. Archive old backups
3. Increase disk allocation

What's Next?

• View Logs - Debug performance issues
• Daily Operations - Monitor your environments