Stay organized with collectionsSave and categorize content based on your preferences.
Request a future reservation for up to 90 days (in calendar mode)
To reserve TPUs for a specific start time and duration, between 1 and 90 days,
request a future reservation in calendar mode. This mode, powered by
theDynamic Workload
Scheduler,
lets you check TPU availability up to 120 days in advance and request capacity
based on your schedule. You can request a future reservation in calendar mode
using the Compute Engine API or Google Cloud console. If approved,
Compute Engine automatically creates a reservation for your chosen date and
time. You can thenconsume the reservationby
provisioning TPUs using theCreate Node APIor
theQueued Resources API. Compute Engine
automatically deletes the reservation, and any TPUs that consume it, at the end
of your reservation period.
Requesting a future reservation for up to 90 days (in calendar mode) is a good
fit for training and experimentation workloads that require precise start times
and have a defined duration.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Request a future reservation for up to 90 days (in calendar mode)\n=================================================================\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nTo reserve TPUs for a specific start time and duration, between 1 and 90 days,\nrequest a future reservation in calendar mode. This mode, powered by\nthe [Dynamic Workload\nScheduler](https://cloud.google.com/blog/products/compute/introducing-dynamic-workload-scheduler),\nlets you check TPU availability up to 120 days in advance and request capacity\nbased on your schedule. You can request a future reservation in calendar mode\nusing the Compute Engine API or Google Cloud console. If approved,\nCompute Engine automatically creates a reservation for your chosen date and\ntime. You can then [consume the reservation](/tpu/docs/consume-reservation) by\nprovisioning TPUs using the [Create Node API](/tpu/docs/managing-tpus-tpu-vm) or\nthe [Queued Resources API](/tpu/docs/queued-resources). Compute Engine\nautomatically deletes the reservation, and any TPUs that consume it, at the end\nof your reservation period.\n\nRequesting a future reservation for up to 90 days (in calendar mode) is a good\nfit for training and experimentation workloads that require precise start times\nand have a defined duration.\n\nFor more information, see [About future reservation requests in calendar\nmode](/compute/docs/instances/future-reservations-calendar-mode-overview).\n\nView future availability of TPUs\n--------------------------------\n\nYou can view the availability of TPUs 1 to 120 days in advance. For more\ninformation, see [View resources future\navailability](/compute/docs/instances/create-future-reservations-calendar-mode#view-availability).\n\nCreate a future reservation request in calendar mode\n----------------------------------------------------\n\nYou can request a future reservation in calendar mode using the Compute Engine\nAPI or Google Cloud console. For more information, see [Create a future reservation\nrequest in calendar\nmode](/compute/docs/instances/create-future-reservations-calendar-mode).\n\nLimitations\n-----------\n\nRequesting a future reservation in calendar mode for TPUs has the following\nlimitations:\n\n- You can't modify, cancel, or delete a future reservation request.\n- You must specify a reservation duration with a minimum of 1 day and a maximum of 90 days.\n- You can only reserve the following TPU versions in the specified zones:\n - **[TPU v6e](/tpu/docs/v6e)**: asia-northeast1-b, us-east5-a, us-east5-b\n - **[TPU v5p](/tpu/docs/v5p)**: us-east5-a\n - **[TPU v5e](/tpu/docs/v5e)** : us-west4-b (`BATCH`), us-central1-a (`SERVING`)\n\n| **Note:** For TPU v5e, you must select a workload type. For workloads that handle large amounts of data in single or multiple operations, such as machine learning (ML) training workloads, specify `BATCH`. For workloads that handle concurrent requests and require minimal network latency, such as ML inference workloads, specify `SERVING`.\n\nFor the allowed number of TPU chips per request, see\n[Limitations](/compute/docs/instances/create-future-reservations-calendar-mode#limitations)\nin the Compute Engine documentation.\n\nWhat's next\n-----------\n\n- [Learn about Cloud TPU reservations](/tpu/docs/about-tpu-reservations)\n- [Share a reservation between projects](/tpu/docs/share-reservation)\n- After your reservation start date, [consume the reservation](/tpu/docs/consume-reservation)"]]
