Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Azure Cosmos DB for PostgreSQL is no longer supported for new projects. Don't use this service for new projects. Instead, use one of these two services:
Use Azure Cosmos DB for NoSQL for a distributed database solution designed for high-scale scenarios with a 99.999% availability service level agreement (SLA), instant autoscale, and automatic failover across multiple regions.
Use the Elastic Clusters feature of Azure Database For PostgreSQL for sharded PostgreSQL using the open-source Citus extension.
Burstable compute on a single node cluster is ideal for workloads like development environments or small databases that don't need the full performance of the node's CPU continuously. These workloads typically have burstable performance requirements.
The Azure burstable compute options allow you to configure a single node with baseline performance that can build up credits when it's using less than its baseline. When the node has accumulated credits, the node can burst above the baseline when your workload requires higher CPU performance. You can use the CPU credits remaining and CPU credits consumed metrics to track accumulated and used credits respectively.
Important
Scaling for burstable compute is available, but only in certain combinations:
- You can change 1 vCore burstable to 2 vCore burstable, and the other way around.
- You can convert a burstable (1 or 2 vCores) single node configuration to
either
- a single node cluster with regular (non-burstable) compute; or
- a multi-node cluster.
You also can't go back from a regular (non-burstable) single node to burstable compute.
Next steps
- See the limits and limitations of burstable compute.
- Review available cluster metrics.