Configuring Keep Warm
You can control how long your containers are kept alive by using thekeep_warm_seconds
flag in your deployment trigger.
For example, by adding a keep_warm_seconds=300
argument to an endpoint, your app will stay running for 5 minutes before shutting off:
When
keep_warm_seconds
is set in your deployment, it will count as billable
usage.Setting Always-On Containers
Any running containers count towards billable usage. Take care to avoid
setting
min_containers
unless you’re comfortable paying for usage 24/7.min_containers
field.
By setting min_containers=1
, 1 container will always remain running until the deployment is stopped.
If you redeploy an app that has
min_containers
set, make sure to explicitly
stop the previous deployment versions in order to avoid running containers
that you are no longer using.Pre-Warming Your Container
You can pre-warm your containers by adding/warmup
to the end of your deployment URL:
/warmup
to the end of any of your deployment APIs to warm-up your container:
Default Container Spin-down Times
After handling a request, Beam keeps containers running (“warm”) for a certain amount of time in order to quickly handle future requests. By default, these are the container “keep warm” times for each deployment type:Deployment Type | Container Keep Warm Duration |
---|---|
Endpoints/ASGI/Realtime | 180s |
Task Queues | 10s |
Pods | 600s |