autoscaling slots

Related topics

• autoscaling slots is part of BigQuery reservations From the official documentation: “In this tutorial, you create a Standard edition reservation with 100 autoscaling slots and assign a project to the reservation.”
• autoscaling slots is part of reservation From the official documentation: “You can specify the number of slots in a reservation as a baseline amount which is always allocated, or as an autoscaled amount, which is allocated when needed.”
• autoscaling slots is part of reservations From the official documentation: “Reservations can include *baseline* slots, which are always allocated, as well as *autoscaled* slots, which are [added or removed dynamically](/bigquery/docs/slots-autoscaling-intro) based on the demands of your workload.”
• Compute Engine configures commitment From the official documentation: “When you enable auto-renewal on a resource-based commitment, each time your commitment reaches the end of its term, Compute Engine automatically renews that commitment for a new term.”
• reservation works with Vertex AI From the official documentation: “You can modify the reservation to allow Vertex AI training or prediction jobs to use it.”
• commitment works with reservation From the official documentation: “When you purchase a new commitment, you can attach reservations to your commitment in either of the following ways:”
• reservations is part of Compute Engine From the official documentation: “Reservations are a Compute Engine feature.”
• commitment depends on reservations From the official documentation: “To get zonal resources at discounted prices and also ensure that capacity is reserved for them, you must both purchase commitments and create reservations for those zonal resources.”
• Compute Engine works with reservation From the official documentation: “After you attach your reservations, Compute Engine automatically populates the fields in the **Commitment details** section to match the numbers and types of resources from your attached reservations.”
• idle slots works with reservation From the official documentation: “A reservation is an isolated pool of resources with the added benefit of being able to take advantage of idle capacity in a given region across your organization.”
• idle slots is part of reservations From the official documentation: “By default, queries running in a reservation automatically use idle slots from other reservations within the same administration project.”
• idle slots works with reservations From the official documentation: “In addition, [idle slots](/bigquery/docs/slots#idle_slots) can be shared across reservations.”
• reservation is part of commitment From the official documentation: “To replace the attached reservation `res-1` with `res-2` for the `my-commitment-with-reservations` commitment, make the following `POST` request by using the [`regionCommitments.updateReservations`](/compute/docs/reference/rest/beta/regionCommitments/updateReservations) method:”
• reservation is part of Compute Engine From the official documentation: “If Google Cloud approves your request, then Compute Engine creates reservations with your requested resources at your specified date and time.”
• reservations works with Vertex AI From the official documentation: “The *sharing policy* specifies if a reservation of GPU VMs can be consumed by [custom training jobs](/vertex-ai/docs/training/overview) or [prediction jobs](/vertex-ai/docs/predictions/overview) in Vertex AI.”