Committed use discounts

Compute Engine lets you purchase committed use contracts in return for deeply discounted prices for VM usage. These discounts are referred to as committed use discounts.

Committed use discounts are ideal for workloads with predictable resource needs. When you purchase a committed use contract, you purchase compute resource (vCPUs, memory, GPUs, and local SSDs) at a discounted price in return for committing to paying for those resources for 1 year or 3 years. The discount is up to 57% for most resources like machine types or GPUs. The discount is up to 70% for memory-optimized machine types. For committed use prices for different machine types, see VM instances pricing.

Committed use discount recommendations give you opportunities to optimize your compute costs by analyzing your VM spending trends with and without a committed use discount contract. By comparing these numbers, you can see how much you can save each month with a committed use contract. To learn more about how commitment recommendations work, you can also review Understanding commitment recommendations.

You can purchase a committed use contract for a single project, or purchase multiple contracts which you can share across many projects by enabling shared discounts.

After purchasing, you are billed monthly for the resources you purchased for the duration of the term you selected, whether or not you use the services. If you have a predictable workload, you can use committed use discounts to help you cut costs on resources that you need.

Committed use discounts work on most Compute Engine machine types, including predefined and custom machine types. Committed use discounts are simple and flexible, and require no upfront costs. Discounts apply to the aggregate number of vCPUs, memory, GPUs, and local SSDs within a region, so they are not affected by changes to your instance's machine setup.

Although N2 and C2 machine cores and memory are included in committed use discount pricing, 50, 75, and 100 Gbps higher bandwidth SKUs are excluded from discounts.

F1-micro and g1-small shared-core machines are not eligible for committed use discounts.

Note: Purchasing a committed use discount does not affect your VM configurations in any way.

Before you begin

• If you want to use the command-line examples in this guide:
  1. Install or update to the latest version of the gcloud command-line tool.
  2. Set a default region and zone.
• If you want to use the API examples in this guide, set up API access.

How committed use discounts work

If you have just a few projects, you can purchase commitments just for the specific resources you plan to use.

For example, if you purchase a commitment for 8 cores, and you run 24 cores during the month, you will receive committed use discounts for 8 cores. The other 16 cores will be billed at standard, non-committed use rates. Keep in mind that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 8 cores, you're billed the committed use rates for those 8 cores for the whole month, even if you might have only run these cores for a part of the month. It is to your advantage to purchase commitments only in increments you know you will use.

Any resources that do not qualify for committed use discounts automatically qualify for sustained use discounts. You can't combine committed use discounts and sustained use discounts for the same resources.

Committed use discounts apply to both vCPUs and memory. You can buy a committed use discount for vCPUs or memory independently of one another.

Commitments can't be stacked for burst scenarios. For example, if you purchased 10 cores for the month and then ran 20 cores for half the month, commitments would not apply for the full 20 cores just because the usage was half the month.

Resources that are not covered by committed use discounts automatically qualify for sustained use discounts on a machine type family basis.

For example:

You run an n2-standard-2 for a portion of the month and run an n2-standard-8 for another portion of the same month, Compute Engine combines the two and applies sustained use discounts for the portion not covered by committed use discounts because both machine types belong to the n2-standard family.

By default, committed use discounts apply at the project level, but you can enable discount sharing from your billing account to share discounts across multiple projects.

Sharing committed use discounts across projects

Sharing your committed use discounts across all your projects reduces the overhead of managing discounts on a per-project basis, and maximizes your savings by pooling all your discounts across your projects' resource usage.

If you have multiple projects that share the same Cloud Billing account, you can enable committed use discount sharing so all of your projects within that Cloud Billing account share all of your committed use discount contracts. Your sustained use discounts are also pooled at the same time. That is, sustained use discounts are calculated using the total resources across these projects, rather than just the resources within a single project.

For example, if you purchase two commitment contracts for a total of 160 cores, and you run 200 cores during the month, you will receive committed use discounts for 160 cores across the projects that used them. The additional 40 cores will be billed at on-demand, non-committed use rates. Note that after you purchase a set amount of commitments, you're billed for those commitments monthly, even if you don't use them. For example, if you purchase commitments for 160 cores, you're billed the committed use rates for those 160 cores for the whole month, even if don't use them. See Understanding discount sharing for cost-saving utilization recommendations.

Note: Committed use discounts do not differentiate between custom machine types and predefined machine types. The discount will be spread proportionally across all projects under the same Cloud Billing account. See Attribution when using custom machine type SKUs for additional information.

Committed use discounts are subject to Google Cloud commitment-based pricing and billing. By purchasing a committed use discount, you agree to these terms. Committed use discounts do not renew, so you must create a new commitment to continue receiving discounts.

Specifications

• You can only purchase commitments if you have quota for commitments. For more information about quotas, see Resource quotas. Check the Quotas page to ensure you have enough quota to create a commitment. If commitments are not listed on the quotas page or you require additional quota, request a quota increase.

• Commitments must be purchased on a per-region basis.

• To use the gcloud tool to manage commitments, you must be running gcloud version 147.0.0 or later. To update the gcloud tool to the latest version:

  gcloud components update
  

  To check the version of the gcloud tool you are running:

  gcloud version
  

• Any remaining vCPUs and memory that are not covered by committed use discounts are eligible for sustained use discounts.

Restrictions

• Committed use discounts automatically apply to VMs by Google Kubernetes Engine, Dataproc, and Compute Engine. Committed use discounts do not apply to VMs created using App Engine flexible environment or Dataflow.
• Projects that are in the free tier period with free tier credit and projects that do not have any payment history do not qualify for committed use discounts.
• You can purchase commitments only on a per-region basis.
• Committed use discounts apply to usage in the project or Cloud Billing account in which those discounts are purchased.
• For commitments shared across projects under one Cloud Billing account: If any part of the commitment is unutilized, the remaining commitment charge remains in the project that purchased that portion of the commitment
• Committed use discounts do not apply to preemptible VM instances, N1 shared-core machine types, or extended memory.
• For committed use discounted pricing for GPUs and local SSDs, you must create a reservation when purchasing the commitment.
• Committed use discount prices are independent of on-demand pricing. Any fluctuation in on-demand pricing would not necessarily be reflected in committed use discounts.
• If a reservation is attached to a committed use discount, the reservation can't be deleted for the duration of the commitment.
• You can only buy a 1-year commitment on K80 GPUs.

Pricing

Committed use discount pricing for VM instances, with or without GPUs or local SSDs, differs depending on the region. For current rates, see Pricing.

Commitment types

You can purchase commitments for the following resources.

Commitment types	Resources for which you can purchase discounts	Applicable to the following resource types
General purpose E2 commitments	vCPUs Memory	All E2 machine types
General purpose N2 commitments	vCPUs Memory Local SSD	All N2 machine types Sole-tenant nodes
General purpose N2D commitments	vCPUs Memory Local SSD	All N2D machine types
General purpose N1 commitments	vCPUs Memory GPUs Local SSD	N1 machine types, excluding shared-core. Sole-tenant nodes GPUs: NVIDIA® T4 NVIDIA® V100 NVIDIA® P100 NVIDIA® P4 NVIDIA® K80
Compute-optimized commitments	vCPUs Memory	Compute-optimized machine types
Memory-optimized commitments	vCPUs Memory	Memory-optimized machine types
Accelerator-optimized A2 commitments	vCPUs Memory GPUs Local SSD	All A2 machine types GPUs: NVIDIA® A100

You can't purchase commitments for f1-micro, or g1-small machine types or for the sole-tenant premium charge.

Commitments for machine types

Purchase the appropriate commitment type for the machine types you are using. Discounts for general-purpose commitments are applied to resources in the following order:

1. E2,N2, N2D, or N1 custom machine types, depending on which commitment you purchase
2. Sole-tenant nodes
3. Either the E2, N2, N2D, or N1 predefined machine types, depending on which commitment you purchase

When you purchase general-purpose commitments, you pick which generation the commitment applies to. For example, if you purchase general-purpose E2 commitments, they only apply to E2 machine types. Similarly, if you purchase general-purpose N2, N2D, or N1 commitments, the commitments never overlap.

For example, assume you have a region with the following mix:

• 10 N2 custom machine type vCPUs
• 30 GB of custom machine type memory
• 2 n2-standard-4 predefined machine types

You purchase N2 commitments for 15 vCPUs and 13.5 GB of memory for committed use. The committed use discounts would be applied first to the N2 custom machine types, and any remaining discounts would be applied to the N2 predefined machine types. In this case, all 10 vCPUs of the N2 custom machine types would be charged at committed use prices, and 13.5 GB of custom machine type memory would be charged at committed use prices.

Finally, the remaining 5 vCPUs of committed use would apply to 5 random vCPUs across the two n2-standard-4 machine types. Any resources that aren't covered by committed use discounts would qualify for sustained use discounts.

Note: Commitments are aggregated by machine family. If you are unsure of how many commitments to purchase, you might want to purchase a smaller number of commitments, then add more as you need them. For example, you can purchase multiple contracts for 10 vCPUs and zero memory, then purchase separate contracts for additional memory.

To purchase a commitment for general-purpose machine types, see Purchasing commitments for machine types.

Memory-optimized commitments

Memory-optimized committed use discounts apply to either M1 or M2 machine types. Quota for these committed use discounts is separate. If you want to use a committed use discount for an M1 machine type, you must have quota for an M1 machine. The same is true for M2—you must have quota for the committed use discount.

If you intend to use memory-optimized machine types, purchase memory-optimized commitments. To purchase a commitment for memory-optimized machine types, see Purchasing commitments for machine types.

Compute-optimized commitments

If you intend to use compute-optimized machine types, purchase compute-optimized commitments. To purchase a commitment for compute-optimized machine types, see Purchasing commitments for machine types.

Accelerator-optimized commitments

If you intend to use accelerator-optimized machine types, purchase accelerator-optimized commitments. To purchase a commitment for accelerator-optimized machine types, see Purchasing commitments for machine types.

Commitments for GPUs and local SSD

To purchase commitments for GPUs or local SSDs, you must also reserve the resources when purchasing the commitment. Reserving these resources is required to ensure that the resources are always available for you (whether you use them or not). There are no additional charges for reserving the resources.

You must purchase commitments by specific GPU types. For example, you can purchase GPUs for either NVIDIA P100s or NVIDIA V100s, but you can't purchase commitments for NVIDIA P100 GPUs and apply them to other GPU types.

To purchase a commitment for GPUs and local SSDs, see Purchasing commitments for GPUs and local SSD.

For more information about reservations, see Reserving zonal resources.

Requesting quota for commitments

You can only purchase commitments if you have quota for commitments. Check the Quotas page to ensure you have enough quota to create a commitment.

When making a request using the gcloud tool or the API, the server returns the following error if you have no commitment quota:

"Quota 'COMMITMENTS' exceeded. Limit: 0.0"

Note: If your project is still in the free tier period with free tier credit remaining, or if your project does not have payment history, it does not qualify for committed use discounts. This means the project is not granted quota to create commitments.

Checking quota in the Cloud Console

Permissions required for this task

To perform this task, you must have the following permissions:

• serviceusage.quotas.get on the project to view quotas.

In the Google Cloud Console, go to Quotas on the IAM & Admin page.

Go to Quotas

The Quotas page lists all of your Compute Engine resource quota and the level of quota usage. A resource with a quota status that is close to its limit is listed at the top of the page in order of most urgent denoted by a warning icon. Toggle the Quota status column to see each resource and its quota usage.

1. In the Details column, click ALL QUOTAS to get usage information.
2. Check the quota for commitments in your desired region. If you do not have quota for a commitment, the Limit is 0.

To request quota in the Cloud Console

Permissions required for this task

To perform this task, you must have the following permissions:

• serviceusage.quotas.get on the project to view quotas.
• serviceusage.quotas.update to request a quota increase.
• Your role determines the level of control you have over requesting more quota.

In the Google Cloud Console, from the Menu, point to IAM & Admin, and click Quotas:

Go to Quotas

1. In the Quota status column, click on . The quota panel lists all of your quotas.
2. Select the checkbox for the location of the quota that needs adjustment.
3. Click EDIT QUOTAS.
4. Complete the request form.
5. Enter your revised quota limit, and optionally, a description.
6. Click DONE.
7. Click SUBMIT REQUEST.

Alternatively, click Filter table to query your quota by a specific property.

You will receive an email in response to your request.

Increasing committed resource quotas

If you do not have enough quota for Committed CPUs, Committed local SSDs, or Committed GPUs (for example, for Committed NVIDIA V100 GPUs), request a quota increase from the Quotas page. To utilize the commitment, you also need sufficient resource quota (for example, NVIDIA V100 GPUs). You can request these quota increases at any time.

To increase your COMMITTED CPU quota, do the following:

1. Submit a new quota request to increase your Committed CPU quota to the new maximum amount you require. For example, if you have 14k vCPUs and you need 20k vCPUs, submit the request for 20k. Wait for the request to be approved and closed before continuing to the next step.
2. Submit a new quota request to increase your Commitments quota to match the number of commitments you require. For example, if you have 10 commitments for 20k vCPUs, you must request quota to cover those 10 commitments.

This increases your committed CPU to match your current maximum CPU quota in the specified region.

Purchasing commitments for machine types

You can purchase commitments for machine types by using the Cloud Console, the gcloud command-line tool, or programmatically, through the API. To purchase commitments for GPUs or local SSDs, see Purchasing commitments for GPUs and local SSDs.

By default, project owners have permission to purchase committed use discount contracts. However, it's possible for owners to create custom roles that include or exclude certain users. Read about access control to ensure you have permission to purchase a committed use discount contract.

After purchasing a commitment, the commitment is effective starting at midnight the following day. For example, a commitment purchased on Monday afternoon at 3 PM PST becomes effective on Tuesday at 12 AM PST. The discounts are automatically applied to applicable instances in the region you specified, and to the projects in which those discounts are purchased.

Important: After you purchase a committment, you can't cancel it.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a commitment for a VM.
• compute.commitments.list to view a list of commitments on a project.

Console

1. In the Google Cloud Console, go to the Committed use discounts page.

   Go to Committed use discounts

2. To purchase a new commitment, click Purchase commitment.

3. Name your commitment.

4. Choose the region where you want it to apply.

5. Choose the Commitment type:
   General-Purpose E2 for E2 machine types
   General-Purpose N2 for N2 machine types
   General-Purpose N2D for N2D machine types
   General-Purpose N1 for N1 machine types
   Compute-optimized for compute-optimized machine types
   Memory-optimized for memory-optimized machine types
   Accelerator-optimized A2 for accelerator-optimized machine types
   

6. Choose a commitment Duration of 1 or 3 years.

7. Enter the quantity of Cores or Memory that you want to purchase. There is no lower limit, the number can be zero. The quantity for cores must be entered as a whole number equal to or greater than zero. Memory can be purchased in increments of 0.25 GB.

8. Read the terms of purchase.

9. Click the Purchase button to purchase the commitment.

gcloud

Using the gcloud tool, run the gcloud compute commitments create command:

gcloud compute commitments create COMMITMENT_NAME \
    --region REGION \
    --resources vcpu=NUMBER_VCPUS,memory=MEMORY \
    --plan DURATION \
    --type COMMITMENT_TYPE

Replace the following:

• COMMITMENT_NAME: the name you want to identify this commitment with.
• REGION: the region this commitment applies to. Each region has different commitment prices. For current prices, see the price sheet.
• NUMBER_VCPUS: the number of vCPUs you are willing to purchase commitments for. The number of vCPUs must be an integer of 0 or more and can be even or odd.
• MEMORY: the amount, in MB or GB, of memory you are willing to purchase commitments for. For example, 1000MB. If the units are not specified, the default unit used is GB. Memory can be purchased in increments of 0.25 GB.
• DURATION: the term of the commitment, either 12-month or 36-month.

• COMMITMENT_TYPE: one of:

  • general-purpose-e2 for general purpose E2 machine type commitments.
  • general-purpose-n2 for general purpose N2 machine type commitments.
  • general-purpose-n2d for general purpose N2D machine type commitments.
  • general-purpose for general purpose N1 machine type commitments.
  • compute-optimized for compute-optimized commitments.
  • memory-optimized for the memory-optimized commitments.

  • (preview) accelerator-optimized for the accelerator-optimized commitments.

    If you do not specify the --type flag, the default value used is general-purpose.

Examples

• To create a general-purpose commitment for N1 machine types, you might use the following example:

  gcloud compute commitments create example-commitment --region us-central1 \
    --resources vcpu=5,memory=33280MB --plan 12-month
  

• To create a compute-optimized commitment, use the gcloud compute commitments create command, which purchases a 1 year commitment for a compute-optimized machine type:

  gcloud compute commitments create example-compute-optimized-commitment \
    --region us-central1 --resources vcpu=2,memory=3814GB --plan 12-month \
    --type compute-optimized
  

• To create a memory-optimized commitment:

  gcloud compute commitments create example-memory-optimized-commitment \
    --region us-central1 --resources vcpu=96,memory=1434MB \
    --plan 12-month --type memory-optimized
  

• To create an accelerator-optimized commitment, you must create a reservation when purchasing the commitment by using the gcloud compute commitments create command. You must also specify the total number of resources (including GPUs) that you need. For example, the following commitment includes 96 vCPUs, 680 GB memory, 8 GPUs, and a reservation for those GPUs to be used in 2 VMs in us-central1-a.

  gcloud compute commitments create example-accelerator-optimized-commitment \
    --region=us-central1 \
    --resources=vcpu=96,memory=680GB \
    --resources-accelerator=type=nvidia-tesla-a100,count=8 \
    --plan 12-month \
    --type accelerator-optimized \
  
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=a2-highgpu-4g \
    --vm-count=2
  
  

• To create a GPU or local SSD commitment, you must create a reservation when purchasing the commitment by using the gcloud compute commitments create command. For example, the following commitment includes 4 GPUs and a reservation for those GPUs to be used in 2 instances in us-central1-a.

  gcloud compute commitments create example-reservation-commitment \
    --region=us-central1 \
    --resources=vcpu=96,memory=624GB \
    --resources-accelerator=type=nvidia-tesla-v100,count=4 \
    --plan 12-month \
    
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=n1-standard-32
    --accelerator=type=nvidia-tesla-v100,count=2 \
    --vm-count=2
    
  

API

In the API, make a POST request to the regionCommitments.insert method, with a request body that contains information about the commitment:

https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments?requestId=OPTIONAL_UNIQUE_ID

Note: requestId is an optional query parameter, but we recommend providing it to help prevent unintended duplicate requests.

The resource body should contain:

• name for the name of the commitment.
• plan for the term of the commitment, either TWELVE_MONTH or THIRTY_SIX_MONTH.
• resources to specify the amount of memory and vCPU. Memory must be be specified in MB. You must specify both VCPU and MEMORY in the resources section.
• type of commitment, either GENERAL_PURPOSE_E2,GENERAL_PURPOSE_N2 GENERAL_PURPOSE_N2D,GENERAL_PURPOSE, COMPUTE_OPTIMIZED, MEMORY_OPTIMIZED, or ACCELERATOR_OPTIMIZED.

For example, the following creates a commitment for 1 year with 5 vCPUs and 18.75 GB of memory:

{
  "name": "example-commitment",
  "plan": "TWELVE_MONTH",
  "type": "GENERAL_PURPOSE",
  "resources": [
    {
    "amount": "5",
    "type": "VCPU"
    },
    {
    "amount": "19200",
    "type": "MEMORY"
    }
  ]
}

To create a memory-optimized commitment, include the type property. The following example shows a purchase of a 1 year commitment for an m1-megamem-96 machine type:

{
  "name": "example-memory-optimized-commitment",
  "plan": "TWELVE_MONTH",
  "type": "MEMORY_OPTIMIZED",
  "resources": [
    {
    "amount": "96",
    "type": "VCPU"
    },
    {
    "amount": "1434",
    "type": "MEMORY"
    }
  ]
}

To create a compute-optimized commitment, include the type property. The following example, purchases a 1 year commitment for a c2-standard-16 machine type:

{
  "name": "example-compute-optimized-commitment",
  "plan": "TWELVE_MONTH",
  "type": "COMPUTE_OPTIMIZED",
  "resources": [
    {
    "amount": "16",
    "type": "VCPU"
    },
    {
    "amount": "1434",
    "type": "MEMORY"
    }
  ]
}

Purchasing commitments for GPUs and local SSDs

Note: The following steps explain how to purchase commitments for GPUs that use the general-purpose N1 machine type. To purchase commitments for NVIDIA A100 GPUs, which are tightly coupled with the A2 machine types, follow the instructions for Purchasing commitments for machine types.

To purchase a commitment for GPUs or local SSDs:

• You must purchase a general-purpose N1 commitment. GPUs are only supported with N1 machine types (with the exception of the A100 GPUs).
• You must create a reservation that includes either GPUs or local SSDs at the same time when you are purchasing your commitment.
• You do not need to commit to vCPUs or memory.

You must purchase commitments for specific GPU types. For example, you might purchase either NVIDIA P100s or NVIDIA V100s, but you cannot purchase commitments for NVIDIA P100 GPUs and expect to apply them to other GPU types.

The amount of GPUs and local SSDs that you reserve must be equal to the amount that you commit to. For example, if you want to reserve 4 V100 GPUs, then you must also commit to 4 V100 GPUs. However, the amount of vCPU and memory that you reserve can be more or less than what you commit to.

If you only want to commit to GPUs or local SSDs, you can specify 0 for vCPU and memory commitments. But the reservation that you attach to your commitment must contain the same GPUs and local SSDs as the commitment, as well as the machine types (with vCPUs and memory) that you want to reserve.

Note: You do not need to specify a commitment type because the commitment automatically defaults to general purpose. You can only purchase GPUs and local SSDs for general-purpose commitments.

Purchase a commitment with an attached reservation using the Cloud Console, the gcloud tool, or the API.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a commitment for a VM.
• compute.commitments.list to view a list of commitments on a project.
• compute.commitments.updateReservations to create a reservation for GPUs or SSDs.

Console

1. In the Google Cloud Console, go to the Committed use discounts page.

   Go to Committed use discounts

2. To purchase a new commitment, click Purchase commitment.

3. Name your commitment, and choose the region where you want it to apply.

4. For Commitment type, select General Purpose.

5. Choose a commitment Duration of 1 or 3 years.

6. Enter the quantity of Cores and Memory that you want to purchase. If you only want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPU and memory commitment quantities.

7. Click Add GPUs and select the GPU type and Number of GPUs that you want to commit to.

8. Click Add local SSD and specify the number of disks that you want to commit to.

9. Click Add new reservation to create one or more reservations for instances that will use the GPUs and local SSDs.

   1. Name your reservation.
   2. Under Use with VM instance:
      • If you want to use this reservation's resources only when creating matching instances that specifically target this reservation by name, select Select specific reservation.
      • If you want matching instances to automatically use this reservation, select Use reservation automatically.
   3. Choose the Zone where you want to reserve resources.
   4. Specify the Number of VM instances that you want to reserve.
   5. Specify the resources that you want to reserve for each instance:
      • If you have an instance template, click Use instance template and select an instance template from the list.
      • Otherwise, click Specify machine type.
        1. Click Customize to use the slider to select the Cores and Memory for your machine type.
        2. Specify the CPU platform.
        3. To add GPUs, enter the number of GPUs and the GPU type.
        4. Optionally, specify the number of Local SSDs that you want to add to each instance and specify the Interface type to use.
   6. Click the Done button to create the reservation.
   Note: The amount of GPUs and local SSDs that you reserve must be equal to the amount that you commit to.

10. Click the Purchase button to purchase the commitment.

11. Read the terms of purchase and click Purchase when you are ready to purchase the commitment.

gcloud

Use the gcloud compute commmitments create command to purchase a commitment, and include flags to create an attached reservation.

For example, the following commitment includes 4 GPUs and a new reservation for those 4 GPUs to be used across 2 n1-standard-32 instances in us-central1-a.

gcloud compute commitments create commitment-01 \
    --region=us-central1 \
    --resources=vcpu=96,memory=624GB \
    --resources-accelerator=type=nvidia-tesla-v100,count=4 \
    --plan 12-month \
    --reservation=reservation-01 \
    --reservation-zone=us-central1-a \
    --machine-type=n1-standard-16 \
    --accelerator=type=nvidia-tesla-v100,count=2 \
    --vm-count=2

If you want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPU and memory commitment quantities.

gcloud compute commitments create commitment-01 \
    --region=us-west2 \
    --resources=vcpu=0,memory=0 \
    --resources-accelerator=type=nvidia-tesla-p4,count=1 \
    --plan 12-month \
    --reservation=reservation-01 \
    --reservation-zone=us-west2-b \
    --machine-type=n1-standard-2 \
    --accelerator=type=nvidia-tesla-p4,count=1 \
    --vm-count=1

To create multiple reservations when purchasing a commitment, use a YAML file that contains the reservation properties. For example:

gcloud compute commitments create commitment-01 \
    --region=us-central1 \
    --resources=vcpu=96,memory=624,local-ssd=750 \
    --resources-accelerator=type=nvidia-tesla-v100,count=1 \
    --plan 12-month \
    --reservations-from-file=YAML_FILE

For example, the following YAML file contains 2 reservations. The first reservation, res-01, contains 1 n1-standard-2 instance with 1 GPU, and it is a targeted reservation, which means that you must specifically target that reservation by name to use its reserved instances. The second reservation, res-02, contains 1 n1-standard-2 VM instance with 2 types of attached local SSDs.

‐ reservation: res-01
  reservation_zone: us-central1-a
  require_specific_reservation: true
  vm_count: 1
  machine_type: n1-standard-2
  accelerator:
  ‐ count: 1
    type: nvidia-tesla-v100
‐ reservation: res-02
  reservation_zone: us-central1-a
  vm_count: 1
  machine_type: n1-standard-2
  local_ssd:
  ‐ interface: scsi
    size: 375
  ‐ interface: nvme
    size: 375

API

Use the regionCommitments.insert method and include the reservations field to define the reservation's properties. For example, the following commitment includes 4 GPUs and a reservation for those 4 GPUs to be used across 2 instances in us-central1-a.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments

{
  "name": "commitment-01",
  "plan": "TWELVE_MONTH",
  "resources":
  [
    {
      "amount": "96",
      "type": "VCPU"
    },
    {
      "amount": "638976",
      "type": "MEMORY"
    },
    {
      "acceleratorType": "nvidia-tesla-v100",
      "amount": "4",
      "type": "ACCELERATOR"
    }
  ],
  "reservations":
  [
    {
      "name": "reservation-01",
      "specificReservation":
      {
        "count": "2",
        "instanceProperties":
        {
          "guestAccelerators":
          [
            {
              "acceleratorCount": 2,
              "acceleratorType": "nvidia-tesla-v100"
            }
          ],
          "machineType": "n1-standard-8"
        }
      },
      "specificReservationRequired": false,
      "zone": "us-central1-a"
    }
  ]
}

If you only want to commit to and reserve GPUs or local SSDs without committing to vCPUs and memory, specify 0 for the vCPU and memory commitment quantities. For example:

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/commitments

{
  "name": "commitment-01",
  "plan": "TWELVE_MONTH",
  "resources":
  [
    {
      "amount": "0",
      "type": "VCPU"
    },
    {
      "amount": "0",
      "type": "MEMORY"
    },
    {
      "acceleratorType": "nvidia-tesla-v100",
      "amount": "4",
      "type": "ACCELERATOR"
    }
  ],
  "reservations":
  [
    {
      "name": "reservation-01",
      "specificReservation":
      {
        "count": "2",
        "instanceProperties":
        {
          "guestAccelerators":
          [
            {
              "acceleratorCount": 2,
              "acceleratorType": "nvidia-tesla-v100"
            }
          ],
          "machineType": "n1-standard-8"
        }
      },
      "specificReservationRequired": false,
      "zone": "us-central1-a"
    }
  ]
}

The commitment is successfully created only if there are enough resources in the target zone, and sufficient quota, at the time of the request.

When you create a commitment with an attached reservation, you cannot delete the reservation for the duration of the commitment. When your commitment expires, Compute Engine automatically deletes any attached reservations.

If you need to transfer GPUs or local SSDs across committed reservations, see Modifying reservations that are attached to commitments.

Purchasing commitments for SLES for SAP premium images

If you run your SAP workloads on VMs running SUSE Linux Enterprise Server (SLES) for SAP, purchasing a committed use discount for your SAP licenses can result in significant cost savings.

When you purchase commitments, they form a "pool" of licenses that automatically apply to your running VM instances within a selected project in a specified region. Discounts apply to any active VMs while VMs spin up and down, so the commitment is not tied to any one particular VM.

For example, you have 10 VMs running in two regions: 5 VMs in us-central1, and 5 VMs in us-west1 under the same project ID. You must purchase 5 licenses in each region to cover those running VMs. You can apply the licenses to any 5 concurrently running VMs at any time during the year in those regions. You are billed monthly for the commitment regardless of your usage.

When commitments expire, your running VMs continue to run at on-demand rates. After you purchase a commitment, you can't cancel it.

Important: Always verify that your contracts are in the correct project ID and regions to avoid being double charged. You must create your committed use discount in the same project and region as the machine using the license. For example, if you create your committed use discount contract in Project A, but the running VMs that require the contracts are in Project B, you are charged for the commitments in Project A and the on-demand price for the VMs running in Project B.

To purchase a commitment for your SAP license you must:

• Purchase a license commitment. You can't edit an existing commitment.
• Purchase a commitment for 1 or 3 years.

Permissions required for this task

To perform this task, you must have the following permissions:

• compute.commitments.create to create a license for committed use discounts.

Purchase an SAP SLES license commitment using the Google Cloud Console, the gcloud command-line tool, or the Compute Engine API.

Console

1. In the Cloud Console, go to the Committed Use Discounts page.

   Go to the Committed Use Discounts page

2. Click Purchase commitment to purchase a new commitment.
3. Click New license committed use discount to purchase a new license commitment.
4. Name your commitment and choose the region where you want it to apply.
5. Choose a duration amount of the commitment, either 1 or 3 years.
6. Choose a License family.
7. Choose the License type and quantity.
8. Choose the Number of licenses.
9. Click Purchase.

gcloud

Using the gcloud tool, run the gcloud compute commitments create-license command to purchase a license commitment.

For example, the following commitment is for an SAP SUSE license for 2 cores for 12 months in the us-central1 region.

gcloud compute commitments create-license COMMITMENT_NAME \
    --license https://www.googleapis.com/compute/v1/projects/PROJECT_ID/global/licenses/LICENSE_TYPE
    --amount NUMBER_OF_LICENSES \
    --cores-per-license CORES_PER_LICENSE \
    --plan PLAN \
    --region REGION \

Replace the following:

• COMMITMENT_NAME: the name for your commitment.
• LICENSE: the license URI. For example: https://www.googleapis.com/compute/v1/projects/PROJECT_ID/global/licenses/LICENSE_TYPE
• NUMBER_OF_LICENSES: the number of licenses you plan to purchase.
• CORES_PER_LICENSE: the number of cores per license Enter 1-2 3-4, or 5+.
• PLAN: enter the plan length: 12-month or 36-month.
• REGION: the region where this commitment applies.
• LICENSE_TYPE: the SAP license type.

API

Use the regionCommitments.insert method and include the licenseResource field to define the commitment's properties. For example, the following commitment includes 4 cores per license, a total of 4 licenses, and the public URI to the example's license resource.

POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/commitments?requestId=OPTIONAL_UNIQUE_ID

{
    "licenseResource":
      "coresPerLicense": "3-4",
      "amount": 4,
      "license": "https://www.googleapis.com/compute/v1/projects/suse-sap-cloud/global/licenses/sles-sap-12"
    }
}

Applying committed use discount recommendations

Committed use discount recommendations are available in the Google Cloud Console. The Recommender generates a card with information about your VM usage over the last 30 days. If your VMs show a trend of uncommitted usage over 30 days, the Recommender classifies this as an opportunity to purchase committed use discounts to reduce your VM costs.

Usage is considered uncommitted and eligible if the following is true.

• The VM was active for the entire duration of the 30 days.
• The VM's SKU is part of an eligible committed use discount bucket.
• The VM's usage was not already covered by an existing commitment.

Recommendations are refreshed once per day and take the last 30 days of usage history into consideration.

Recommendations for committed use discounts are generated by two separate algorithms, which you can select from when purchasing (or accepting) them on the summary card.

• Stable usage recommendations cover minimum stable usage over time.
• Optimal recommendations are based on overall usage and might cover resources that are not on all the time.

You can read more about committed use recommendations at Understanding commitment recommendations in the billing documentation.

Limitations

Committed use discount recommendations are available for the CPU and memory component of machine type commitments only. Committed use discount recommendations are not available for SSD, GPU or license commitments.

Reviewing and accepting a recommendation

From the Google Cloud Console dashboard:

1. Select your project name.
2. Click Recommendations. The Recommender card displays Recommended Compute Engine Commitments.
3. Click the linked recommendation to open the card and view your estimated savings with a committed use discount contract.
4. Toggle between 1-year and 3-year to see your savings. For a more complete description of the card's information, see Reading recommendation summary cards.
5. Click Continue to purchase at the bottom of the card to proceed with the committed use contract.
6. Complete the process to purchase a commitment.

If you have more than one VM that can benefit from a committed use discount, you can click View all from the card and review each VM individually.

Dismissing a recommendation

If you don't want to see your recommendations, you can dismiss them by specific VM or dismiss the entire card. You must restore recommendations to see them again.

Turning on committed use discount sharing

By default, committed use discounts are applied to the project from which you purchased it. To share the discount across multiple projects linked to your Cloud Billing account, enable committed use discount sharing from the console.

You must have specific permissions to access billing account information. Read the Overview of Cloud Billing access control document for specifics.

1. Sign in to Cloud Billing in the Google Cloud Console.

   Sign in to Cloud Billing

   If you have more than one Cloud Billing account, do one of the following:

   • To manage Cloud Billing for the current project, select Go to linked billing account.
   • To locate a different Cloud Billing account, select Manage billing accounts and then choose the account that you want to manage.

2. From the Billing navigation menu, select Commitments.

3. Click on view committed use discount analysis.

4. Select Commitment Scope from the top of the page.

   • Project scope is the default option when you select committed use discounts for a specific project. To change your setting, you must enable shared billing.

5. Type Enable in the text entry box to enable Billing account scope commitments.

6. Click Enable Billing Account Scope to save your changes.

Important: It can take up to 24 hours for a new commitment scope to take effect. After 24 hours, confirm your billing scope is set to Billing Discount. If it isn't, contact Google Cloud Support.

When you enable committed use discount sharing, all of your current active committed use discounts in all the projects under the same Cloud Billing account, including those you previously purchased and new ones you purchase in the future are shared across your Cloud Billing account. Your sustained use discounts are also pooled and shared across all projects within your Cloud Billing account. When you change your commitment scope configuration, the change takes effect on the following day at midnight Pacific Standard Time (PST).

To gain a better understanding of how committed use discounts impact and appear on your bill, see Understanding your bill with committed use discounts.

Important: Once you enable discount sharing through the console, you can only disable it with the assistance of Cloud Billing support. If you disable discount sharing with the assistance of Cloud Billing support, all committed use discounts revert to the default setting of applying only to the projects through which with they were purchased. The reverted setting becomes effective at the beginning of the following month.

Combining reservations with commitments

A committed use discount provides a 1- or 3-year discounted price agreement, but it does not reserve capacity in a specific zone. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running. By combining a reservation with a commitment, you get discounted, reserved resources.

To purchase a commitment and get discounted prices for GPUs and local SSDs, create a reservation when purchasing the commitment. For these resources, the location and size of the reservation can't be changed for the duration of your commitment.

For information about reservations, see Combining reservations with committed use discounts.

Modifying a commitment

After you purchase a commitment, you can't change it. If you need to modify a commitment, purchase a new commitment with a new expiration date for the incremental amount.

For example, if you want to increase the amount of vCPUs for a commitment from 10 vCPUs to 15 vCPUs, purchase a new commitment for the difference. In this case, purchase a new commitment for 5 vCPUs.

You can't decrease the resources already purchased in a commitment. For example, you can't change a commitment for 15 vCPUs to 10 vCPUs.

Viewing active commitments

View commitments in the console or the API.

Console

In the Google Cloud Console, view a list of commitments in the Committed use discounts page.

Go to Committed use discounts

gcloud

Make a request using the commitments list command:

gcloud compute commitments list

The tool returns a list of commitments:

 NAME              REGION    END_TIMESTAMP                  STATUS
 my-commitment     us-east1  2018-03-17T00:00:00.000-07:00  NOT_YET_ACTIVE

API

You can get a list of commitments across all regions by making an aggregatedList request to the following URL:

https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/aggregated/commitments

Which returns a list of commitments:

"commitments": [
{
  "kind": "compute#commitment",
  "id": "3294122326373778983",
  "creationTimestamp": "2017-02-09T15:18:32.411-08:00",
  "name": "example-commitment",
  "region": "https://www.googleapis.com/compute/v1/projects/example-project/regions/us-central1",
  "selfLink": "https://www.googleapis.com/compute/v1/projects/example-project/regions/us-central1/commitments/example-commitment",
  "status": "NOT_YET_ACTIVE",
  "statusMessage": "The commitment is not yet active (its startTimestamp is in the future). It will not apply to current resource usage.",
  "plan": "TWELVE_MONTH",
  "startTimestamp": "2017-02-10T00:00:00.000-08:00",
  "endTimestamp": "2018-02-10T00:00:00.000-08:00",
  "resources": [
    {
      "type": "VCPU",
      "amount": "5"
    },
    {
      "type": "MEMORY",
      "amount": "32500"
    }]
  }
]

A commitment can have one of the following statuses:

• CREATING: the commitment is being created.
• NOT_YET_ACTIVE: the commitment has been created but is not yet active. Commitments are effective at midnight the following day.
• ACTIVE: the commitment is active.
• EXPIRED: the commitment has expired. Compute Engine reserves the right to remove expired commitments that are older than 210 days from the expiration date.

Changing a commitment

It is not possible to edit your commitment. To increase your commitment, you must create a new commitment with the resources you want to add. This is a separate commitment with its own expiration date. It will not be merged with your existing commitment.

Canceling a commitment

After you create a commitment, you can't cancel it. You must pay the agreed upon monthly amount for the duration of the commitment. Commitments are not affected by future pricing changes to the standard prices for Compute Engine resources.

If you accidentally purchased a commitment or made a mistake configuring your commitment, contact Google Cloud billing support for help.

Understanding your bill with committed use discounts

Read the following documents to gain a better understanding of your billing:

• View and download the cost details of your invoice or statement.
• Analyze the effectiveness of your committed use discounts.
• Understand your savings with cost breakdown reports.

Support

If you have any questions regarding committed use discounts on your bill, you can contact Google Cloud support.

What's next

• Create some instances with custom machine types.
• Review pricing information for committed use discounts.