This document explains Cloud Bigtable pricing details. You can also use the Google Cloud Platform Pricing Calculator to estimate the cost of using Cloud Bigtable.
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Overview
When you use Cloud Bigtable, you are charged for the following:
- The type of Cloud Bigtable instance, and the total number of nodes in your instance's clusters.
- The amount of storage that your tables use.
- The amount of network bandwidth that you use.
When you enable replication by creating an instance with 2 clusters, you are charged only for the items listed above, including the complete copy of the instance's data that is stored with the second cluster. There are no additional charges for replication beyond these standard items.
Storage and bandwidth usage are measured in binary gigabytes (GB), where 1 GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB).
Storage and bandwidth charges accrue daily. You can view unbilled usage at any time on the Google Cloud Platform Console.
The following sections show the pricing for each component of Cloud Bigtable.
Instance type and nodes
For production instances, Cloud Bigtable keeps track of how many Cloud Bigtable nodes exist in your instance's clusters during each hour. You are charged each hour for the maximum number of nodes that exist during that hour, multiplied by the hourly rate. As a result, any nodes that you provision will be billed for a minimum of one hour.
For development instances, you are billed a flat rate for each hour.
| Instance type | Cost |
|---|---|
| Production instance | |
| Development instance | |
|
In a production instance that uses SSD storage, each node will typically deliver 10,000 QPS and 10 MB/s on random reads and writes. Parallel scans can deliver around 220 MB/s per node. Performance will vary depending on row sizes and data access patterns, and instances that use HDD storage will have lower performance. For more information, see our performance guide. Development instances are for testing and development. They have no performance or uptime guarantees, and the SLA does not apply. |
|
Storage
Cloud Bigtable frequently measures the average amount of data in your Cloud Bigtable tables during a short time interval. For billing purposes, these measurements are combined into an average over a one-month period, and this average is multiplied by the monthly rate.
You are billed only for the storage you use, including overhead for indexing and Cloud Bigtable's internal representation on disk. For instances that contain 2 clusters, Cloud Bigtable keeps a separate copy of your data with every cluster, and you are charged for every copy of your data.
When you delete data from Cloud Bigtable, the data becomes inaccessible immediately; however, you are charged for storage of the data until Cloud Bigtable compacts the table. This process typically takes up to a week.
In addition, if you store multiple versions of a value in a table cell, or if you have set an expiration time for one of your table's column families, you can read the obsolete and expired values until Cloud Bigtable completes garbage collection for the table. You are also charged for the obsolete and expired values prior to garbage collection. This process typically takes up to a week.
| SSD storage (GB/mo) | HDD storage (GB/mo) |
|---|---|
Network
Some types of network egress traffic are subject to bandwidth charges, as shown below.
| Ingress | Free |
| Egress to the same zone | Free |
| Egress between zones in the same region | Free |
| Egress between regions within the US (per GB) | $0.01 |
| Inter-continental egress | At Internet egress rate |
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Internet egress rates
| Monthly Usage | Egress to Worldwide Destinations (excluding Asia & Australia) (per GB) |
Egress to Asia Destinations (excluding China, but including Hong Kong) (per GB) |
Egress to China Destinations (excluding Hong Kong) (per GB) |
Egress to Australia Destinations (per GB) |
Ingress |
|---|---|---|---|---|---|
| 0-1 TB | $0.23 | $0.19 | Free | ||
| 1-10 TB | $0.22 | $0.18 | Free | ||
| 10+ TB | $0.20 | $0.15 | Free |
Pricing example: Single instance without replication
Suppose you have a Cloud Bigtable instance that has only 1 cluster, with no replication. During a 30-day billing cycle, you use the following Cloud Bigtable resources:
- 1 production instance in
us-central1(Iowa) with a single cluster, which has 18 nodes during days 1-10 and 25 nodes during days 11-30 - Average of 30 TB of data stored on SSD drives in
us-central1 - 10 TB of network ingress to
us-central1 - 50 GB of network egress to
us-central1 - 25 GB of network egress to
EU
Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.
Cloud Bigtable nodes
- 1 cluster * 18 nodes * 10 days * 24 hours/day * $0.65
per node per hour in
us-central1: $2,808.00 - 1 cluster * 25 nodes * 20 days * 24 hours/day * $0.65
per node per hour in
us-central1: $3,900.00
Storage
1 cluster * 30 TB * 1,024 GB/TB * $0.17 per GB in
us-central1: $5,222.40
Network
- 10 TB of ingress to
us-central1: No charge - 50 GB of egress to
us-central1: No charge - 25 GB of egress to
EU* $0.12 per GB: $3.00
Monthly total
In this example, the total monthly bill for Cloud Bigtable is $11,933.40.
Pricing example: Single instance with replication
Suppose you have a Cloud Bigtable instance that has 2 clusters, which means that replication is enabled. During a 30-day billing cycle, you use the following Cloud Bigtable resources:
- 1 production instance in
us-central1(Iowa) with 2 clusters; each cluster has 18 nodes during days 1-10 and 25 nodes during days 11-30 - Average of 30 TB of data stored on SSD drives in
us-central1 - 10 TB of network ingress to
us-central1 - 50 GB of network egress to
us-central1 - 25 GB of network egress to
EU
Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.
Cloud Bigtable nodes
- 2 clusters * 18 nodes * 10 days * 24 hours/day * $0.65
per node per hour in
us-central1: $5,616.00 - 2 clusters * 25 nodes * 20 days * 24 hours/day * $0.65
per node per hour in
us-central1: $7,800.00
Storage
2 clusters * 30 TB * 1,024 GB/TB * $0.17 per GB in us-central1:
$10,444.80
Network
- 10 TB of ingress to
us-central1: No charge - 50 GB of egress to
us-central1: No charge - 25 GB of egress to
EU* $0.12 per GB: $3.00
Monthly total
In this example, the total monthly bill for Cloud Bigtable is $23,863.80.
