Sandbox Runtimes and Resource Limits
Select a compute shape and expiration duration for each sandbox, and a timeout for each command.
Runtime
The managed runtime uses Oracle Linux with Python 3.11. Select python-3.11 when creating a sandbox. To supply your own image, see Using a Custom Image for a Sandbox.
Compute Shapes
| Shape | OCPUs | Memory |
|---|---|---|
SMALL
|
1 | 4 GB |
MEDIUM
|
2 | 8 GB |
LARGE
|
4 | 16 GB |
Duration and Timeouts
Set the sandbox's initial lifetime with expirationDuration in the API or --expiration-duration in the CLI. The maximum requested initial duration is 48 hours. Use ISO 8601 durations, such as PT5M for five minutes, PT30M for 30 minutes, or PT1H for one hour.
To add time to a running sandbox, use the extend operation before it expires. Extensions are subject to service limits. See Extending a Running Sandbox.
Each command has a separate timeout. Set it to the time the command needs and ensure that enough sandbox lifetime remains. A command timeout doesn't extend the sandbox's expiration.
Snapshots have a separate expiration duration. Project response and conversation retention settings don't configure sandbox or snapshot lifetimes.
Capacity
Ensure that your tenancy has enough sandbox CPU and memory capacity for the sandboxes and warm pools you plan to create. See Service Limits for information about viewing limits and requesting increases.