Committed use discounts (CUDs) for Memorystore for Memcached provide deeply discounted prices in exchange for your commitment to continuously use a certain amount of Memorystore for Memcached capacity for a year or longer.
Memorystore for Memcached CUD commitments are fungible with Memorystore for Redis instances.
Memorystore for Memcached CUDs are ideal when your spending on Memorystore for Memcached capacity involves a predictable minimum that you can commit to for at least a year.
Memorystore for Memcached CUD pricing
Memorystore for Memcached CUDs offer two levels of discounts, depending on the commitment period:
A one-year CUD gives you a 20 percent discount from the on-demand rate.
A three-year CUD gives you a 40 percent discount from the on-demand rate.
When you purchase a CUD, you choose a one or three-year period, as well as a commitment amount: your expected Memorystore for Memcached expenditure on capacity per hour over that period. This commitment amount, after the application of your discount, becomes your commitment fee. You are then billed for this commitment fee on a monthly basis for the duration of the CUD's period. (For a full example, see An example Memorystore for Memcached CUD, below.)
The discount applies to any eligible usage of Memorystore for Memcached, Memorystore for Redis, or Memorystore for Redis Cluster instances associated with the Cloud Billing account used to purchase the CUD, with the exception of Memorystore for Redis M1 capacity tier instances (less than 5 GB). For information on resources that are ineligible for Memorystore CUDs, see Resources eligible for Memorystore for Memcached CUDs.
Any expenditure beyond the commitment gets billed at the on-demand rate. As your Memorystore for Memcached usage grows, you can purchase additional CUDs to receive discounts on increased expenditures not covered by previous commitments.
If Memorystore for Memcached's on-demand rates change after you purchase a CUD, your commitment fee does not change, and you still receive the same discount percentage on applicable usage.
Resources eligible for Memorystore for Memcached CUDs
Memorystore for Memcached committed use discounts automatically apply to your spending on Memorystore for Memcached, Memorystore for Redis, and Memorystore for Redis Cluster instances for your billing account. This flexibility helps you achieve a high utilization rate of your commitment across regions and projects without manual intervention, saving you time and money.
Memorystore for Memcached CUDs do not apply to your spending on Cloud Storage storage, backup, outbound data transfer, or Memorystore for Redis M1 capacity tier instances (less than 5 GB).
Supported regions
Memorystore for Memcached committed use discounts are supported in the following regions:
Region ID | Region description | ||
---|---|---|---|
asia-east1 | Taiwan | ||
asia-east2 | Hong Kong | ||
asia-northeast1 | Tokyo | ||
asia-northeast2 | Osaka | ||
asia-northeast3 | Seoul | ||
asia-south1 | Mumbai | ||
asia-south2 | Delhi | ||
asia-southeast1 | Singapore | ||
asia-southeast2 | Jakarta | ||
australia-southeast1 | Sydney | ||
australia-southeast2 | Melbourne | ||
europe-central2 | Warsaw | ||
europe-north1 | Finland | ||
europe-southwest1 | Madrid | ||
europe-west1 | Belgium | ||
europe-west12 | Turin | ||
europe-west2 | London | ||
europe-west3 | Frankfurt | ||
europe-west4 | Netherlands | ||
europe-west6 | Zurich | ||
europe-west8 | Milan | ||
europe-west9 | Paris | ||
me-central1 | Doha | ||
me-west1 | Tel Aviv | ||
northamerica-northeast1 | Montréal | ||
northamerica-northeast2 | Toronto | ||
southamerica-east1 | São Paulo | ||
southamerica-west1 | Santiago | ||
us-central1 | Iowa | ||
us-east1 | South Carolina | ||
us-east4 | Northern Virginia | ||
us-east5 | Columbus | ||
us-south1 | Dallas | ||
us-west1 | Oregon | ||
us-west2 | Los Angeles | ||
us-west3 | Salt Lake City | ||
us-west4 | Las Vegas |
Purchase a Memorystore for Memcached CUD
To purchase or manage Memorystore for Memcached committed use discounts for your Cloud Billing account, you must have a Billing Account Administrator role with that account.
You can purchase a Memorystore for Memcached CUD in the Google Cloud console billing page. Select the Commitments tab, then select the PURCHASE action at the top. Read the Purchasing spend-based commitments section in Google Cloud's documentation for more details.
After purchasing a CUD, the commitment goes into effect within the next hour. Its discounts are automatically applied to subsequent eligible usage.
Please note that, after your purchase a CUD, you cannot cancel its commitment. Make sure the size and duration of your commitment aligns with both your historical and your expected minimum expenditure on Memorystore for Memcached capacity.
In addition, before you purchase a commitment, please read the Service Specific Terms regarding Committed Units.
An example Memorystore for Memcached CUD scenario
Your commitment should represent your expected minimum hourly expenditure on Memorystore for Memcached capacity across your projects over the next one or three years.
As an example, say that you have a Memorystore for Memcached instance in the
us-central1
region. This instance has 15 nodes of size 10 GB each, and each
node has 4 vCPUs.
From the pricing page, you can calculate the approximate hourly commitment cost:
- Expenditure in
us-central1
: (15 nodes * 10 GB per node * $0.0089 price per GB per hour = $1.335 per hour) + (15 nodes * 4 vCPUs per node * $0.05 price per vCPU per hour) = $4.335 price per hour
If you expect to spend that minimum of $4.335 per hour continuously for
the next year or more, then you can make a commitment for that amount.
In other words, when purchasing that CUD, you would round up and enter "$4.34
"
as the hourly on-demand commitment amount.
If, on the other hand, you expect to scale down the capacity occasionally, you can make a commitment for a lower amount. Any expenditure above that limit is charged at the on-demand rate.
Continuing this example, assume that you do decide on a commitment of $4.34 per hour. As your next step, you choose the length of the commitment's period.
As a basis for comparison, compute the on-demand cost of Memorystore for Memcached compute capacity at the chosen commitment rate, without the application of any commitment discounts:
- Monthly cost based on on-demand pricing: $4.34 per hour * 730 hours = $3,168.20 per month.
From here, you can calculate the monthly costs and savings you would see under a 1-year CUD, applying its 20% discount, compared to a year of paying the full on-demand rates:
- Monthly cost of a 1-year, $4.34/hour commitment: ($4.34 per hour - 20% discount) * 730 hours = $2,534.56 per month
- Total savings per month: $3,168.20 - $2,534.56 = $633.64
- Total savings with a 1-year, $4.34/hour commitment: $633.64 per month * 12 months = $7,603.68
You can apply similar math to calculating the costs and savings of a 3-year CUD, with its 40% discount compared to on-demand rates:
- Monthly cost of a 3-year, $4.34/hour commitment: ($4.34 per hour - 40% discount) * 730 hours = $1,900.92 per month
- Total savings per month: $3,168.20 - $1,900.92 = $1,267.28
- Total savings with a 3-year, $4.34/hour CUD: $1,265.82 per month * 36 months = $45,622.08
As you can see, a commitment that covers your expected minimum Memorystore for Memcached usage over the years to come can lead to significant savings. Read on for our recommendations on choosing the right CUD size for your Memorystore for Memcached projects.
Recommendations for choosing a commitment
While considering the purchase of Memorystore for Memcached CUDs, keep in mind the following:
Regions: Memorystore for Memcached CUDs apply across regions. If you have Memorystore for Memcached instances in multiple regions, calculate the expenditure across all the regions while making a commitment.
Projects: Determine the consistent baseline expenditure per project while calculating total commitment. Consider that production loads usually run 100% of the time, while development or staging environments may often run intermittently.
Instances: If you frequently scale your instances up or down, consider purchasing CUDs only for their baseline predictable usage. If you have instances that you run only for bursts or brief durations, exclude them from your calculations.
Your commitment fee applies to every hour during the term of the commitment, regardless of actual usage. Choose your CUD's commitment amount carefully, based on both your historical Memorystore for Memcached usage and your future expectations. As long as your use of Memorystore for Memcached capacity stays above your committed expenditure level, you will enjoy the maximum possible discount for the length of that commitment.
What's next
Learn how to view your CUD reports.
Understand savings with cost breakdown reports.