31 lines
1.7 KiB
Plaintext
31 lines
1.7 KiB
Plaintext
---
|
|
title: Set instance allocation limits
|
|
description: Set, view, and change how much time an instance is allowed to use.
|
|
platform: cloud
|
|
---
|
|
# Set instance allocation limits
|
|
|
|
An account might have allotted time on the Premium or Flex plan. Because each account can have many instances on a plan, setting allocation limits helps you control which instances are allowed to consume that time. Note that if the allocation is not set as a limit, the instance can use more than its allotted time.
|
|
|
|
The time that you allocate to instances is used by the fair-share algorithm to determine the priority in the queue, based on usage of all QPUs over a rolling time window of 28 days (for Premium Plan users) or over the subscription period (for Flex Plan users).
|
|
|
|
The allocation is set when creating the instance. However, you can view and change allocated time on the [instances page.](https://quantum.cloud.ibm.com/instances)
|
|
|
|
|
|
## What happens when the limit is reached
|
|
|
|
You can optionally set the time allocation as a limit for the instance. The following happens when an instance reaches its limit:
|
|
|
|
- Active workloads continue running.
|
|
- Pending jobs remain queued.
|
|
- No workloads are canceled.
|
|
- Collaborators can submit new workloads, which will remain queued until more time is available.
|
|
- For the Flex Plan, the instance cannot process more jobs unless the limit has been increased or, for the Premium Plan, after the next usage window starts.
|
|
|
|
## Next steps
|
|
|
|
<Admonition type="tip" title="Recommendations">
|
|
- Learn about [instances.](/docs/guides/instances)
|
|
- Review suggestions to [minimize job quantum time.](minimize-time)
|
|
- Understand the [fair-share scheduler.](/docs/guides/fair-share-scheduler)
|
|
</Admonition> |