Memorystore for Redis pricing

This document explains Memorystore pricing details. You can also use the Google Cloud Pricing Calculator to estimate the cost of using Memorystore.

If you want information about pricing for Memorystore for Memcached, view the Memorystore for Memcached pricing page.

Pricing overview

Memorystore pricing is based on the following components:

  • Service tier: Determines whether the Redis instance is standalone or highly available.

  • Provisioned capacity: Determines how much storage and throughput is available to the Redis instance.

  • Region: Determines the location where the Redis instance is provisioned.

Service tiers

Memorystore provides the following tiers of service:

  • Basic Tier: Provides a standalone Redis instance. Use this tier for applications that require a simple Redis cache.

  • Standard Tier: Provides a highly available Redis instance that includes automatically enabled cross-zone replication and automatic failover. Use this tier for applications that require high availability for a Redis instance.

Provisioned capacity

When you provision a Memorystore instance, you choose its maximum storage capacity. The instance falls into a capacity tier based on its provisioned capacity. For example, a 3 GB instance falls into the 1 to 4 GB capacity tier. The capacity tier that the instance falls into affects the following:

  • The price that you pay for the provisioned capacity. For example, if you provision a 3 GB Basic instance, you are charged based on the M1 Basic price for the region the instance is provisioned in.

  • The maximum throughput that you can achieve with the Redis instance. For example, if your application requires a maximum throughput of at least 5 Gbps, you should provision an instance with at least 36 GB of storage, which would put the instance in the M4 capacity tier.

Instance pricing

Pricing depends on the service tier, provisioned capacity, and region where the instance is provisioned. You are charged for a Memorystore instance in 1-second increments, based on the instance's provisioned capacity in GB. The table below shows the price per GB for a full hour (3,600 seconds).

To see Basic Tier and Standard Tier pricing, select a region from the drop-down list above the following table:

Charges are incurred as follows:

  • Pricing is rounded up to the nearest second.
  • Your project starts incurring Memorystore charges when you create a Redis instance. Whether you use the instance or not, you are charged based on the provisioned capacity.
  • You can change the capacity of a Memorystore instance at any time. If the updated capacity causes your instance to fall into a different capacity tier, you are charged based on the new capacity tier as soon as Memorystore completes the scaling operation.

Network pricing

Memorystore traffic must stay within the region where the instance is located. There is no charge for ingress to or egress from Memorystore. You may be charged for network egress from other Google Cloud services, such as from Compute Engine to Memorystore.

Pricing examples

To calculate the per-hour cost of an instance, multiply the provisioned capacity with the unit price for the corresponding capacity tier.

  • Calculating a Basic Tier M2 instance: If you provision a Basic Tier 8 GB instance, the corresponding capacity tier for 8 GB is M2. The unit cost for a Basic Tier M2 instance in the Iowa region is $0.027 per GB per hour. The hourly cost is 8 * $0.027, which is approximately $0.22 per hour or $160.60 per month ($0.22 * 730).

  • Running and scaling a Standard Tier M3 instance: If you provision a Standard Tier 20 GB instance in the Iowa region and run the instance for 90 minutes, you are charged $1.38 (20 GB * $0.046 GB per hr * 1.5 hours). If you change your Standard Tier M3 instance's provisioned capacity from 20 GB to a 50 GB (M4) instance, you are charged the M4 price ($0.035 GB per hr) when the scaling operation completes.

You can also use the Memorystore Pricing Calculator to get pricing estimates for your Memorystore usage scenarios.

What's next