Fluid compute
Burst and elasticity settings for dynamic workloads.
Last updated: 2026-03-17
Fluid compute lets workloads scale based on demand.
When to use
- Spiky traffic
- Background tasks
- APIs with unpredictable bursts
What to monitor
- Cold starts
- Request latency
- Scale events
Safe usage pattern
- Enable fluid compute in non-prod first.
- Define min/max boundaries to avoid runaway scaling.
- Monitor first 24 hours for burst behavior.
- Tune thresholds using observed metrics, not assumptions.
Troubleshooting
Scaling happens too late
- Lower trigger thresholds or increase minimum warm capacity.
Cost spikes during bursts
- Review burst limits and apply stricter max boundaries.