Compute Container Limits

Compute Quota

Once a container starts running, the system will charge for the compute resources based on runtime. Users can view their quota balance for different resources on the "Account Settings" - "Resource Usage" page.

The running system will prioritize deducting fees from the compute resources displayed on this page, with charges applied once per hour by default. When the compute time quota here is exhausted, the system will begin deducting from the user's account balance. If the user's balance is insufficient to pay for the currently running compute resources, the system will stop running the compute container.

Compute Concurrency Limits

To prevent computing resources from being monopolized by a few users, there are limits on the number of compute containers that can be running simultaneously for different compute types. Each user has different limits, which can be viewed in "Account Settings" - "Resource Usage" - "Quota Limits".

Once the concurrency limit for a certain compute type is reached, attempting to create another compute container will result in an error message in the upper right corner of the page: "Resource RTX-3090 exceeds personal limit".

Automatic Container Cleanup

When all executions under a container are closed, meaning there are no active executions, the container will enter the automatic cleanup process. If no new executions are started within the specified time, or if no cleanup of execution records is performed, the container will be considered unused and will be automatically deleted by the system after the specified cleanup time.

Corresponding reminders can also be seen on the container list page.

Creating a new execution or restarting the workspace under the container will refresh the container's automatic cleanup time.

Containers That Will Not Be Automatically Cleaned

If a container does not have an automatic cleanup marker, it means the container will not be automatically cleaned. Containers in the following situations will not be automatically cleaned:

1. Public containers
2. Containers under organizations

Data repositories are not subject to automatic cleanup and will not be automatically cleaned.